# Entity Resolution Anomaly Reporting

Source: https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/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.

```text
N records resolved to D distinct entities, and K of them hold more than one <distinction field>. Matching used a composite threshold of T across: <matching fields>
```

When exactly one entity holds more than one value, the verb agrees with it: `and 1 of them holds more than one`.

Each matching field is listed with the weight configured for it, as `full_name (w=1.0)`, and a field set to consider term frequency carries the tag inside the same brackets, as `full_name (w=1.0+TF)`. When the check blocks on a field, the list opens with `blocked on [<field>],`. See [How It Works](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/how-it-works/) for what the weights do.

## 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

- **Examples**

  Production scenarios with sample records, cluster outcomes, and the resulting anomaly messages.

  [Examples](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/examples/)
- **Best Practices**

  Guidelines for blocking, weighting, tuning the threshold, and normalizing values before resolution.

  [Best Practices](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/best-practices/)
- **Permissions**

  The team permission each action needs: view, create, edit, archive, restore, and delete.

  [Permissions](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/permissions/)
- **How It Works**

  The complete reference: definition, field scope, field roles, comparison types, weights, threshold, and clustering.

  [How It Works](https://userguide.qualytics.io/data-quality-checks/entity-resolution/deep-dive/how-it-works/)

*Last updated: September 22, 2026.*
