Inferensys

Glossary

Entity Resolution

The computational process of identifying and merging disparate records that refer to the same real-world entity across different data sources, creating a unified, authoritative view.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
DEFINITION

What is Entity Resolution?

Entity Resolution is the computational process of identifying, linking, and merging disparate data records that refer to the same real-world entity across different data sources, despite inconsistencies, errors, or variations in representation.

Entity Resolution (ER), also known as record linkage or deduplication, systematically determines whether two or more records correspond to the same physical or conceptual object. The process applies probabilistic matching algorithms, deterministic rule-based logic, or machine learning classifiers to compare attributes like names, addresses, and identifiers. A critical function within master data management (MDM) and knowledge graph construction, ER resolves semantic ambiguity to create a unified, non-redundant view of entities such as customers, products, or locations.

Modern implementations leverage blocking techniques and locality-sensitive hashing (LSH) to reduce the quadratic computational complexity of pairwise comparisons across massive datasets. The output is a golden record or a cluster of linked identifiers that serves as the canonical reference. This process is foundational for entity linking pipelines, enabling accurate knowledge base completion and ensuring that downstream GraphRAG systems retrieve information grounded in a deduplicated, authoritative factual core.

IDENTITY MATCHING

Core Entity Resolution Techniques

The foundational algorithms and data structures used to determine if two or more disparate records refer to the same real-world entity, despite variations in formatting, errors, or missing data.

01

Deterministic Matching

A rule-based approach where records are linked if they agree exactly or within predefined tolerances on a set of identifier attributes. This method relies on exact matching or fuzzy matching on fields like Social Security Numbers or email addresses.

  • Pros: Highly precise, fast, and easily auditable.
  • Cons: Brittle; fails when data contains typos, transpositions, or missing values.
  • Example: Linking customer records where first_name, last_name, and date_of_birth are identical.
100%
Precision Target
02

Probabilistic Matching

Uses statistical models to estimate the likelihood that a pair of records refers to the same entity, even when attributes disagree. The Fellegi-Sunter model is the classic framework, calculating agreement and disagreement weights for each field.

  • Key Concept: A field match on a rare value (e.g., a unique nickname) provides stronger evidence than a match on a common value (e.g., 'John').
  • Output: A confidence score between 0 and 1, allowing for tiered review workflows.
Fellegi-Sunter
Classic Model
03

Blocking and Indexing

A performance optimization technique that avoids the computationally prohibitive O(n²) comparison of all record pairs. Records are partitioned into blocks using a blocking key (e.g., Zip Code or Soundex of last name), and comparisons are restricted to records within the same block.

  • Sorted Neighborhood Method: Slides a window over records sorted by a key, comparing only nearby records.
  • Canopy Clustering: Uses a cheap, high-recall similarity measure to create overlapping clusters for subsequent detailed comparison.
> 95%
Pairs Reduction
04

Machine Learning-Based Resolution

Employs supervised, unsupervised, or active learning models to classify record pairs as matches or non-matches. Feature vectors are constructed from field-level similarity scores (e.g., Jaccard, Levenshtein, TF-IDF cosine distance).

  • Supervised: Requires labeled training data of known duplicates and distinct records.
  • Unsupervised: Uses clustering algorithms like DBSCAN on embedding vectors to group similar records without labeled examples.
  • Active Learning: Iteratively queries a human oracle to label the most informative, uncertain pairs to efficiently train a model.
DBSCAN
Common Clustering
05

Graph-Based Resolution

Represents records as nodes and their pairwise similarity scores as weighted edges in a graph. Entity resolution becomes a community detection or graph partitioning problem.

  • Connected Components: A simple transitive closure—if A matches B, and B matches C, then A, B, and C are the same entity.
  • Correlation Clustering: A more sophisticated global optimization that partitions the graph to minimize disagreements (non-match edges within a cluster, match edges across clusters), resolving inconsistencies in pairwise decisions.
Transitive
Closure Logic
06

Incremental & Real-Time Resolution

Processes new or updated records without re-executing the entire batch resolution pipeline. This is critical for operational systems like Change Data Capture (CDC) feeds.

  • Indexed Lookup: A new record is hashed and compared only against a small set of candidate golden records retrieved via a high-speed index.
  • Delta Processing: Only blocks affected by the new or modified record are re-evaluated, maintaining the integrity of the master data without a full recomputation.
< 1 sec
Latency Target
DISAMBIGUATION GUIDE

Entity Resolution vs. Related Concepts

Distinguishing the core task of merging records from adjacent data quality and identity management disciplines.

CapabilityEntity ResolutionMaster Data ManagementNamed Entity Recognition

Primary Objective

Merge duplicate records into a single golden record

Govern and synchronize master data across the enterprise

Locate and classify named entities in unstructured text

Input Data Type

Structured records from databases

Structured master data domains

Unstructured natural language text

Output

Clustered record groups with a canonical identifier

A single, authoritative source of truth

Annotated text spans with entity labels

Core Mechanism

Fuzzy matching, probabilistic linkage, graph clustering

Workflow orchestration, data stewardship, hierarchy management

Token classification, sequence labeling, transformer models

Handles Unstructured Text

Requires Human Stewardship

Real-Time Operation

Batch or streaming

Batch-oriented

Real-time inference

Related Standard

SHACL for validation

ISO 8000 for data quality

CoNLL for annotation format

ENTITY RESOLUTION

Frequently Asked Questions

Clear, technical answers to the most common questions about identifying, linking, and merging disparate records that refer to the same real-world entity.

Entity resolution (ER), also known as record linkage or deduplication, is the computational process of identifying and merging disparate records that refer to the same real-world entity across different data sources. It works by first blocking records into candidate pairs to avoid an O(n²) comparison, then applying similarity functions (like Levenshtein distance, Jaccard index, or TF-IDF cosine similarity) to compare attributes. Pairs scoring above a threshold are classified as matches using either deterministic rule-based logic or probabilistic models like the Fellegi-Sunter algorithm. Modern systems often use graph embeddings and locality-sensitive hashing (LSH) to scale to billions of records. The final step clusters matched records and merges them into a single golden record with the most accurate, complete attribute values.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.