Inferensys

Glossary

Entity Resolution

The computational process of disambiguating and linking disparate data records that refer to the same real-world entity, critical for unmasking hidden beneficial owners in anti-money laundering.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
IDENTITY DISAMBIGUATION

What is Entity Resolution?

Entity resolution is the computational process of identifying and linking disparate data records that refer to the same real-world entity, despite variations, errors, or inconsistencies in how those records are represented.

Entity resolution (also known as record linkage, deduplication, or identity matching) is the algorithmic process of determining whether two or more data records correspond to the same real-world entity—such as a person, organization, or asset—across heterogeneous datasets. It resolves structural and semantic heterogeneity by analyzing attributes like names, addresses, and identifiers, applying fuzzy matching, phonetic encoding, and probabilistic scoring to overcome inconsistencies caused by typos, transliteration differences, and deliberate obfuscation.

In anti-money laundering and financial crime investigations, entity resolution is critical for piercing through shell corporations and complex ownership structures to unmask hidden beneficial owners. By constructing a unified, deduplicated view of entities across siloed systems, it enables network analysis to reveal collusion rings and layering schemes that would remain invisible when examining records in isolation, directly supporting Know Your Customer and Customer Due Diligence obligations.

UNMASKING HIDDEN CONNECTIONS

Core Capabilities of Entity Resolution

Entity resolution is the computational engine that powers modern financial crime investigations. These core capabilities transform fragmented, inconsistent data into a unified view of real-world actors, enabling analysts to pierce through shell corporations and complex layering schemes.

01

Deterministic Record Linkage

The rule-based matching of records using exact or partial key agreement. This foundational capability applies predefined logic to join datasets where identifiers match precisely.

  • Exact Matching: Joins records on a shared unique key, such as a tax ID or passport number.
  • Rule-Based Matching: Applies cascading logic, e.g., "Match if SSN matches OR (Name AND Date of Birth match)".
  • Phonetic Encoding: Uses algorithms like Soundex or Metaphone to index names by pronunciation, catching spelling variations like 'Smith' vs. 'Smyth'.

While fast and explainable, deterministic methods fail when records contain typos, transliteration errors, or deliberate obfuscation.

Sub-millisecond
Per-comparison latency
02

Probabilistic Fuzzy Matching

A statistical approach that computes the likelihood that two records refer to the same entity despite discrepancies. It uses field-level similarity scores weighted by discriminatory power.

  • Token-Based Similarity: Algorithms like Jaccard Index and TF-IDF measure overlap between sets of words or n-grams.
  • Edit Distance: Levenshtein and Damerau-Levenshtein distances quantify the number of character changes needed to make two strings identical.
  • Weighted Scoring: The Fellegi-Sunter model assigns agreement and disagreement weights to each field, producing a composite match probability.

This method is essential for screening against sanctions lists where names are transliterated from non-Latin scripts.

03

Machine Learning-Based Matching

Supervised and unsupervised models that learn complex matching rules from labeled data or latent patterns, outperforming manual rules on dirty, real-world datasets.

  • Supervised Classification: Models like XGBoost or neural networks trained on labeled pairs of duplicates and non-duplicates to predict match probability.
  • Active Learning: Iteratively queries a human analyst to label the most uncertain pairs, dramatically reducing manual review effort.
  • Clustering for Deduplication: Unsupervised algorithms like DBSCAN or hierarchical agglomerative clustering group records into entity clusters without pre-labeled examples.

These models automatically learn that 'Robert' and 'Bob' are equivalent, adapting to cultural naming conventions.

04

Graph-Based Identity Resolution

Leverages the connected structure of data to resolve identities through relationships, not just attribute similarity. This is critical for uncovering hidden beneficial owners.

  • Entity Relational Graphs: Constructs a network where nodes are entities and edges are shared attributes like phone numbers, addresses, or IP addresses.
  • Community Detection: Algorithms like Louvain or Label Propagation identify tightly connected clusters that likely represent a single real-world actor or collusive ring.
  • Collective Resolution: A change to one entity's linkage propagates across the graph, resolving entire neighborhoods simultaneously.

A fraudster using multiple synthetic identities but a single shared address will be collapsed into one entity through graph analysis.

05

Blocking and Indexing

The performance optimization layer that prevents the computationally prohibitive comparison of every record against every other record. Blocking reduces the search space by orders of magnitude.

  • Standard Blocking: Partitions the dataset into blocks based on a blocking key, such as the first three characters of a surname or a ZIP code. Only records within the same block are compared.
  • Sorted Neighborhood: Slides a window over records sorted by a key, comparing only records within the window.
  • Canopy Clustering: Uses a cheap, approximate distance metric to create overlapping clusters, then performs expensive comparisons only within each canopy.

Without blocking, resolving a database of 10 million records would require 50 trillion pairwise comparisons.

06

Identity Resolution in Motion

Real-time entity resolution at the point of transaction or customer interaction, enabling instantaneous risk decisions rather than batch retrospective analysis.

  • Streaming Deduplication: Integrates with Apache Kafka or Flink to resolve identities against a master entity index in under 100 milliseconds.
  • Incremental Clustering: Updates entity clusters on-the-fly as new transactions arrive, without recomputing the entire database.
  • Cache-First Architecture: Maintains a hot cache of active entity profiles in Redis or similar in-memory stores for sub-millisecond lookups.

This capability allows a payment system to recognize that a new account is linked to a previously blocked entity before the transaction is authorized.

< 100 ms
Decision latency
ENTITY RESOLUTION

Frequently Asked Questions

Clear, technical answers to the most common questions about the computational process of disambiguating and linking disparate data 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 data records that refer to the same real-world entity—whether a person, organization, or object—across one or more databases. The process works by first blocking records into candidate pairs to avoid an O(n²) comparison explosion, then applying similarity functions (e.g., Jaccard, Levenshtein, cosine similarity on embeddings) to compare attributes like names, addresses, and dates of birth. These similarity scores feed into a matching model—either deterministic rule-based systems or probabilistic classifiers trained via Expectation-Maximization or supervised learning—that outputs a match/no-match decision. Finally, clustering algorithms (e.g., connected components, hierarchical agglomerative clustering) group all matching records into a single canonical entity cluster, often assigning a persistent surviving master record or golden record. In anti-money laundering contexts, ER is critical for piercing through shell corporations and synthetic identities to unmask the true beneficial owner behind complex corporate structures.

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.