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.
Glossary
Entity Resolution

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.
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.
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.
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, anddate_of_birthare identical.
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.
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.
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.
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.
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.
Entity Resolution vs. Related Concepts
Distinguishing the core task of merging records from adjacent data quality and identity management disciplines.
| Capability | Entity Resolution | Master Data Management | Named 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 |
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.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Entity Resolution is a foundational process within the knowledge graph construction pipeline. Mastery requires understanding its adjacent concepts, from the data models that store resolved entities to the algorithms that power matching and the standards that ensure interoperability.
Named Entity Recognition (NER)
An information extraction subtask that locates and classifies named entities in unstructured text into predefined categories such as persons, organizations, and locations. NER is a critical pre-processing step for entity resolution on text corpora.
- Input: Raw, unstructured documents.
- Output: Tagged spans of text with labels like
PERSONorORG. - Resolution Dependency: You cannot resolve an entity you haven't first identified. NER provides the candidate mentions for downstream resolution pipelines.
Entity Linking
The NLP task of mapping ambiguous textual mentions of entities to their unique canonical identifiers in a knowledge base like Wikidata. While Entity Resolution merges records within your data, Entity Linking connects your data to the outside world.
- Disambiguation: Resolves 'Apple' to the company
Q312or the fruitQ89. - KB Anchoring: Provides a universal, machine-readable ID for a real-world object.
- Synergy: A resolved internal golden record can be linked to a Wikidata ID for rich external context enrichment.
Locality-Sensitive Hashing (LSH)
An algorithmic technique that hashes similar input items into the same buckets with high probability, enabling efficient approximate nearest neighbor search for deduplication. LSH is a core performance optimization for blocking in entity resolution.
- Blocking: Avoids the O(n²) problem of comparing every record to every other record.
- MinHash: A popular LSH family for estimating Jaccard similarity between text sets.
- Performance: Reduces comparisons from billions to millions by only matching records within the same hash bucket.
Master Data Management (MDM)
A comprehensive methodology for defining and managing an organization's critical data entities to provide a single, authoritative point of reference. Entity Resolution is the technical engine inside an MDM strategy.
- Governance: MDM adds the policies, stewardship, and workflows around the resolution process.
- Domains: Customer (CDM), Product (PDM), Supplier, etc.
- Implementation Styles: Registry, Consolidation, Coexistence, and Centralized—each using entity resolution differently.
Graph Embedding
A dimensionality reduction technique that maps nodes, edges, or entire subgraphs into a low-dimensional vector space while preserving the graph's topological structure. This enables similarity-based entity resolution using vector distance.
- Node2Vec/TransE: Algorithms that learn embeddings by predicting graph context or relationships.
- Vector Similarity: Resolved entities have embeddings that are close in vector space.
- Use Case: Identifying that
node_Aandnode_Blikely represent the same entity because their graph neighborhoods and attributes produce highly similar embedding vectors.

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us