Inferensys

Glossary

Entity Resolution

The computational process of identifying, linking, and merging disparate records that refer to the same real-world entity across different data sources.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
IDENTITY MATCHING

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.

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.

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.

IDENTITY RESOLUTION FOUNDATIONS

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.

01

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.
95%+
Precision achievable with hybrid models
02

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_Code group 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.
03

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.
04

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.
O(n log n)
Complexity with effective blocking
05

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.
06

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.
ENTITY RESOLUTION

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.

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.