Skip to content

Glossary

Entity resolution

Entity resolution determines which records refer to the same real-world entity and which refer to different ones.

Identity and entity resolution

Entity resolution is the task of deciding whether records from one or more sources denote the same real-world thing. Names and addresses are evidence, not identity itself: they can change, be shared or be recorded incorrectly. The task includes both linking true matches and keeping distinct entities apart. It also requires defining the level of identity, such as a legal organization rather than its parent group.

In practice, records are compared using identifiers, names, locations, dates and other contextual attributes. Candidate comparisons may be restricted for efficiency, then reviewed against explicit match criteria. A match decision can be uncertain or time-dependent. Merging records should preserve the original source records and the reason for the identity decision so later evidence can challenge it.

For an organization acting on a record, a false merge can contaminate every associated claim, while a missed match can split the history of one subject. Record linkage is a closely related statistical formulation; entity disambiguation emphasizes selecting the intended referent in context; a canonical identifier is a stable handle for the resolved identity.

Example

A filing for Halden Therapeutics AG (fictional) and a similarly named fictional distributor are kept separate despite a shared city.

The stages of a typical pipeline

Entity resolution is commonly described as a sequence. Records are first standardised, so that names, addresses and dates are in a comparable form. Blocking then reduces the number of pairs to compare. Pairwise comparison scores each candidate pair on several fields; the Fellegi–Sunter model is the classical probabilistic basis, and modern systems often use learned classifiers. A decision step classifies pairs as match, non-match or possible match, and clustering combines pairwise decisions into groups of records denoting one entity, which must be done carefully because a chain of plausible pairs can link records that do not belong together. A final step assigns a stable canonical identifier to each group.

Two surveys give the overview: Christophides and colleagues on entity resolution for big data, and Binette and Steorts, who review the field from its statistical origins to current methods. Both stress that the steps interact: a loose blocking rule limits the recall of everything that follows, and a clustering rule can overturn individually reasonable pairwise decisions.

Evaluating resolution honestly

Pairwise precision and recall are the usual measures, and they can mislead. Because most pairs are non-matches, accuracy is meaningless; because clusters are built transitively, a single wrong link can merge two large groups, which pairwise counts understate. A fuller evaluation looks at cluster-level measures, at the effect on the downstream decision, and at the errors that matter most to the use. Merging two different companies has different consequences from failing to merge two records of one company, and the threshold should reflect that asymmetry. The article on entity resolution evaluation beyond pairwise F1 covers these measures in detail.

Resolution decisions should be reversible and explainable. A merge that cannot be undone, or that records only that two records were joined and not why, converts an uncertain judgment into a permanent fact. The article on merging or relating organisation records argues for keeping the decision as a link with a stated confidence and basis, and merging for presentation only, so that a correction does not require reconstructing history.

A worked example

Three records appear in different systems: Halden Therapeutics AG (fictional) with a registry number; Halden Therapeutics with a Zurich address and no number; and Halden Pharma GmbH with an address in the same building. Standardisation lowercases and strips legal suffixes. The first two share a normalised name and city and score highly, and the registry number resolves the first with a commercial register entry. The third shares the address but differs in name and legal form, so it scores as a possible match and goes to review. The review finds it is a separate company in the same group. The final structure has two entities and a stated group relationship, with the possible-match decision recorded. A system that merged on address alone would have produced one entity with an incorrect legal form.

Related terms and boundaries

Resolution is the broader goal, of which record linkage is the pairwise core and entity disambiguation is the version that links a mention in text to an entry in a reference list. Its output supports golden records and master data management, and its quality limits every later step of data fusion, since an identity error produces conflicts that are not real.

Checks a reviewer can run

Ask for the match thresholds and the proportion of pairs sent to review. Sample links and non-links and check them by hand. Ask how a wrong merge is undone. Ask for the cluster-level error rate and not only the pairwise one. Confirm that decisions are logged with their basis and score.

Common misreadings

  • Equating name similarity with identity.
  • Ignoring parent and subsidiary boundaries.
  • Discarding the evidence behind a merge.

Related terms

Appears in

Found an error on this page? See corrections for what counts as one, how to report it and the dated log.

Enquiry

Where does "Entity resolution" bear on a decision of yours?

This entry sits under identity and entity resolution. If a decision in your organization turns on it, send the entity concerned, the sources you fuse to describe it and who may read which of them. We reply with what a first record would cover.

Or write to [email protected] in your own words.