Entity Resolution Recipe
The Entity Resolution recipe is a guided flow around the existing Entity Resolution rule type. It is not a new rule type. The recipe helps you pick the distinction field, the compare fields, and the match threshold, creates an ordinary Entity Resolution check from them, validates that check on a sample, scans every record, and then groups the duplicates it found so you can choose the records to keep and write them as a golden set to your enrichment destination.
The check the recipe creates is an ordinary quality check. It stays Active after the recipe finishes, so future scans keep catching new duplicates, and the anomalies they raise can bring you straight back into the recipe's Remediate step.
This Deep Dive covers:
- The two phases, Build & Validate and Scan & Remediate, and the steps inside each
- The two prerequisites that block the flow: a profiled table, and a linked enrichment destination before the Scan step
- What the run produces: the check, the scan, the anomaly, the golden set, and the optional output of excluded records
- The entry points that pull an existing check or anomaly into the flow, and how progress is kept
- Examples, best practices, and the permissions behind each step
For the rule's own semantics, such as how blocking and comparison fields score a pair or how clusters become entities, see How Entity Resolution Checks Work.
What You Will Find Here
-
How It Works
The phases, the two prerequisites, what the run reads and writes, and AgentQ's role.
-
Build and Validate
Select Asset, Distinction Field, Compare Fields, Match Threshold, Review, and Validate, step by step.
-
Scan and Remediate
The full scan, choosing golden records, writing the golden set, and the completion summary.
-
Entry Points and Resuming
Open in Recipe, Scan in Recipe, Remediate in Recipe, and how progress is kept between visits.
-
Examples
Real scenarios showing the recipe taking a table from suspected duplicates to a golden set.
-
Best Practices
Guidelines for preparing the asset, choosing fields, tuning the threshold, and remediating.
-
Permissions
The roles and team permissions behind each step of the recipe.