Entity resolution (also known as record linkage or deduplication) systematically determines whether two or more records represent the same real-world person, organization, or object. It operates by comparing attributes—such as names, addresses, and dates of birth—using similarity metrics like Levenshtein distance and Jaro-Winkler similarity to quantify the likelihood of a match when exact keys are unavailable or corrupted.
Glossary
Entity Resolution

What is Entity Resolution?
Entity resolution is the computational process of identifying, linking, and merging disparate records that refer to the same real-world entity across different data sources, despite the absence of a common unique identifier.
To scale to millions of records, entity resolution employs blocking keys to partition data into candidate subsets, drastically reducing the quadratic comparison space. Advanced implementations leverage probabilistic record linkage via the Fellegi-Sunter model, which computes match probabilities using likelihood ratios, or graph-based entity resolution, where records form nodes and similarity scores define edges for community detection algorithms to resolve distinct identity clusters.
Core Characteristics of Entity Resolution
Entity resolution is a multi-stage computational pipeline that transforms fragmented, inconsistent records into a unified, deduplicated view of real-world identities. The following characteristics define its operational architecture.
Deterministic vs. Probabilistic Matching
Entity resolution engines operate on a spectrum between rigid rule-based logic and statistical inference.
- Deterministic Matching: Requires exact agreement on a predefined combination of identifiers (e.g., SSN + DOB). It is fast and auditable but fails against typos or intentional obfuscation.
- Probabilistic Matching: Uses the Fellegi-Sunter model to calculate match likelihoods based on attribute agreement and disagreement patterns, tolerating real-world data noise.
- Hybrid Approaches: Modern production systems often cascade deterministic blocking keys with probabilistic scoring to balance speed and recall.
Blocking and Indexing for Scale
Comparing every record against every other record is computationally intractable (O(n²)). Blocking partitions datasets into mutually exclusive buckets to drastically reduce comparisons.
- Blocking Keys: Derived attributes like
Soundex(LastName) + ZIP_Codegroup likely matches into the same block. - Sorted Neighborhood: A sliding window passes over sorted records, comparing only those within a fixed distance.
- Canopy Clustering: Uses cheap, high-recall similarity metrics to create overlapping clusters before applying expensive, high-precision comparisons.
- Locality-Sensitive Hashing (LSH): Hashes high-dimensional vectors (like TF-IDF embeddings) so similar items collide in the same bucket with high probability.
Similarity Metrics and Feature Engineering
The accuracy of entity resolution depends on selecting the right distance functions for each attribute type.
- String Fields: Levenshtein Distance for general typos; Jaro-Winkler for personal names where prefix matching matters; Soundex or Metaphone for phonetic normalization.
- Numeric Fields: Absolute difference or percentage tolerance for age; exact match for immutable identifiers.
- Text Fields: TF-IDF Vectorization followed by Cosine Similarity to compare addresses or business descriptions as semantic vectors.
- Temporal Fields: Date proximity scoring with configurable decay windows.
- Composite Scoring: Individual attribute similarities are aggregated into a weighted sum, with weights often learned via machine learning rather than manually assigned.
Graph-Based Resolution and Clustering
Pairwise matching alone is insufficient; records must be clustered into connected components representing distinct identities.
- Identity Clustering: Transforms pairwise match decisions into a graph where nodes are records and edges represent a match above threshold.
- Connected Components: The simplest clustering method—any path between two nodes merges them into the same entity.
- Community Detection: Algorithms like Louvain or Label Propagation identify tightly connected subgraphs, useful for detecting synthetic identity rings.
- Link Prediction: Graph neural networks predict missing edges, inferring hidden relationships between seemingly unconnected records—critical for uncovering fraud rings using stolen identity fragments.
Privacy-Preserving Resolution
When matching records across organizational boundaries—such as between banks for AML compliance—plaintext PII cannot be shared. Cryptographic protocols enable resolution without exposure.
- Bloom Filter Encoding: Sensitive attributes are hashed into irreversible bit arrays, allowing fuzzy matching via set overlap metrics like Dice coefficient without revealing original values.
- Homomorphic Encryption: Allows computation on encrypted data, producing encrypted match results that only the data owner can decrypt.
- Secure Multi-Party Computation (SMPC): Multiple parties jointly compute a matching function without revealing their private inputs to each other.
- Differential Privacy: Adds calibrated noise to match results to prevent inference attacks on individual records.
Incremental and Streaming Resolution
Entity resolution is not a one-time batch operation. Production systems must handle continuous data ingestion and evolving identities.
- Incremental Deduplication: New records are compared against existing resolved entities without recomputing the entire graph.
- Merge and Unmerge Logic: Systems must support rollback when a previously merged entity is later determined to be distinct due to new evidence.
- Temporal Decay: Match confidence decays over time for attributes that change (addresses, phone numbers), preventing stale links.
- Stream Processing: Real-time fraud systems perform entity resolution on event streams using sliding windows and in-memory state stores, resolving identities in milliseconds before transaction authorization.
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.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the computational process of 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, linking, and merging disparate records that refer to the same real-world entity across different data sources. It works by first applying blocking keys to partition large datasets into manageable blocks, drastically reducing the number of pairwise comparisons. Candidate record pairs are then compared using similarity metrics like cosine similarity on vectorized text or Jaro-Winkler similarity on names. The system calculates a composite match score, and pairs exceeding a threshold are classified as matches. Advanced implementations use the Fellegi-Sunter model for probabilistic classification, assigning likelihood ratios to agreement patterns. Finally, linked records are clustered into canonical entity representations using identity clustering or graph-based entity resolution techniques, creating a single, deduplicated view of each identity.
Related Terms
Entity resolution relies on a constellation of interconnected techniques spanning record linkage, graph analytics, and identity verification. The following concepts form the technical foundation for detecting and dismantling synthetic identity fraud.
Fuzzy Matching
A string comparison technique that calculates the probability of two text strings being a match, tolerating typographical errors, abbreviations, and formatting inconsistencies. Essential for resolving identities where names like 'Robert Smith' and 'Bob Smyth' may refer to the same individual.
- Levenshtein Distance: Measures minimum single-character edits required to transform one string into another
- Jaro-Winkler Similarity: Optimized for short strings like personal names, giving higher weight to matching prefixes
- Soundex: Phonetic algorithm indexing names by pronunciation, converting 'Smith' and 'Smyth' to the same code
These algorithms are the workhorses of entity resolution pipelines, applied to names, addresses, and organizational identifiers.
Probabilistic Record Linkage
A statistical framework formalized by the Fellegi-Sunter model that uses likelihood ratios to calculate match probabilities between record pairs without relying on deterministic keys. This approach is critical when identifiers are noisy or deliberately obfuscated.
- Agreement weights: Quantify the evidentiary value of matching fields
- Disagreement weights: Penalize mismatches proportionally to field reliability
- Threshold optimization: Balances false positives against false negatives using Expectation-Maximization algorithms
The model estimates the probability that two records belong to the same entity given observed agreement patterns across multiple attributes, enabling robust identity resolution even with intentionally corrupted data.
Graph-Based Entity Resolution
An approach that models records as nodes and their pairwise similarity scores as edges in a graph, applying community detection or clustering algorithms to resolve entities. This method excels at uncovering synthetic identity rings where fraudsters create multiple interconnected fake profiles.
- Connected components: Identifies clusters of records all linked by high similarity scores
- Community detection: Algorithms like Louvain or Label Propagation partition the graph into distinct identity clusters
- Link prediction: Estimates the probability of hidden connections between seemingly unrelated identities
Graph-based methods reveal the structural patterns of fraud rings that pairwise comparison alone would miss, exposing the coordinated nature of synthetic identity attacks.
Blocking Keys
A performance optimization technique that partitions large datasets into mutually exclusive blocks using a common attribute, drastically reducing the number of record pair comparisons required. Without blocking, comparing 100 million records would require approximately 5 quadrillion pairwise comparisons.
- Standard blocking: Groups records by exact match on a key like ZIP code or birth year
- Sorted neighborhood: Sorts records by a blocking key and compares only within a sliding window
- Canopy clustering: Uses cheap, approximate distance metrics to create overlapping blocks
Effective blocking strategies reduce computational complexity from O(n²) to near-linear time while maintaining high recall, making real-time entity resolution feasible at scale.
Privacy-Preserving Record Linkage
A cryptographic protocol that enables the matching of records across disparate databases without revealing the plaintext personally identifiable information (PII) to any party. This is essential when financial institutions collaborate to detect synthetic identities spanning multiple organizations.
- Bloom filter encoding: Converts sensitive attributes into irreversible bit arrays that support fuzzy matching
- Homomorphic encryption: Allows computation on encrypted data without decryption
- Secure multi-party computation: Distributes computation so no single party sees the full dataset
These techniques enable consortium-based fraud detection while maintaining compliance with regulations like GDPR and CCPA, allowing banks to share identity intelligence without exposing customer data.

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