Entity Resolution Anomaly Reporting

This page explains how the Entity Resolution check reports a violation. It covers the anomaly message the check produces, what each number in it means, how the offending clusters appear in Source Records, and why per-row reporting does not apply.

Anomaly Messages

Entity Resolution produces one Shape Anomaly for the check. The violation belongs to a cluster of records rather than one individual field value, so the check does not produce Record Anomalies.

N records were resolved to D distinct entities (composite threshold T: field_a (w=W), field_b (w=W) ...). K of those entities are assigned more than one value of <distinction_field>

When block fields exist, the message includes blocked on [...].

What the Numbers Mean

• N: distinct records analyzed after filtering, block-field NULL handling, and de-duplication.
• D: entity clusters produced.
• T: configured composite match threshold.
• K: clusters with more than one distinction-field value.

Source Records Behavior

Source Records include only non-compliant clusters. Within each cluster, the anomaly shows one example row for each distinct value of the distinction field. Every row includes _qualytics_entity_id so the cluster boundaries are visible.

Custom Anomaly Description

Custom Anomaly Description does not apply to this rule. The option replaces the message on Record Anomalies, and Entity Resolution emits a Shape Anomaly only: the violation belongs to a cluster of records, not to a single row.

See Also