Inferensys

Glossary

Identity Resolution

Identity resolution is the data management discipline of accurately matching and merging identity data across disparate systems to create a unified, 360-degree view of a customer, patient, or organization.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.

What is Identity Resolution?

Identity resolution is the data management discipline of accurately matching and merging identity data across disparate systems to create a unified, 360-degree view of a customer, patient, or organization.

Identity resolution is the computational process of determining whether multiple records from heterogeneous source systems represent the same real-world entity, despite inconsistencies in data formatting, missing values, or temporal changes. It combines record linkage, fuzzy matching, and probabilistic matching algorithms to assign a persistent canonical entity identifier that unifies fragmented data silos into a single golden record.

Unlike simple deduplication, enterprise identity resolution must handle complex many-to-many relationships, privacy-preserving constraints via privacy-preserving record linkage (PPRL), and real-time matching at scale. The resulting unified identity graph serves as the foundational data layer for master data management (MDM) initiatives, enabling accurate analytics, personalization, and compliance across the organization.

UNIFIED ENTITY VIEW

Core Identity Resolution Techniques

The foundational methods used to match and merge disparate identity records into a single, accurate, 360-degree view of a customer, patient, or organization.

01

Deterministic Matching

A rule-based approach that links records only when a specific set of identifiers match exactly. This method relies on a unique, high-quality key such as an email address, Social Security Number, or a composite key of multiple fields.

  • Mechanism: Boolean logic (AND/OR rules) on exact field comparisons.
  • Use Case: Ideal for systems with clean, standardized data and a reliable universal identifier.
  • Limitation: Fails on typographical errors, nicknames, or missing data; generates high precision but low recall.
100%
Precision Target
02

Probabilistic Record Linkage

A statistical framework, formalized by the Fellegi-Sunter model, that calculates match weights for record pairs based on the agreement and disagreement patterns of multiple attributes. It estimates the probability that two records refer to the same entity without requiring exact matches.

  • Key Metrics: Agreement weight (m-probability) and disagreement weight (u-probability).
  • Advantage: Tolerates noise, typos, and missing data by using frequency-based likelihood ratios.
  • Output: A composite score that can be thresholded to classify pairs as matches, non-matches, or potential matches for clerical review.
Fellegi-Sunter
Statistical Foundation
03

Fuzzy Matching

A string comparison technique that calculates the edit distance or similarity between two text strings to identify non-exact duplicates. It tolerates typographical errors, abbreviations, and formatting inconsistencies.

  • Algorithms: Levenshtein distance, Jaro-Winkler, Soundex, and n-gram similarity.
  • Application: Used to compare names ('Jon' vs 'John'), addresses ('St.' vs 'Street'), and other semi-structured text fields.
  • Critical Tuning: Requires careful threshold setting to balance false positives against false negatives.
04

Blocking

A computational efficiency technique that partitions datasets into mutually exclusive blocks using a cheap heuristic, drastically reducing the number of required pairwise comparisons from a Cartesian product to manageable subsets.

  • Goal: Avoid O(n²) complexity by only comparing records within the same block.
  • Common Keys: Phonetic encoding (Soundex), zip code, or first letter of the last name.
  • Trade-off: Reduces computational load but risks missing true matches that fall across block boundaries (pair completeness vs. reduction ratio).
O(n²) → O(n)
Complexity Reduction
05

Machine Learning-Based Resolution

Uses supervised, unsupervised, or active learning models to classify record pairs as matches or non-matches. Modern approaches leverage transformer-based neural networks and entity embeddings to capture semantic similarity beyond surface-form string matching.

  • Features: Vector similarity of name/address embeddings, temporal proximity, and relationship graph connectivity.
  • Clustering: Algorithms like DBSCAN or hierarchical agglomerative clustering group all records belonging to the same entity.
  • Advantage: Adapts to domain-specific patterns and improves over time with human-in-the-loop feedback.
06

Privacy-Preserving Record Linkage (PPRL)

A set of cryptographic and encoding techniques that allows the linkage of records across databases without revealing the plaintext personally identifiable information (PII) to any party.

  • Techniques: Bloom filter encoding, homomorphic encryption, and secure multi-party computation.
  • Use Case: Critical for inter-hospital patient matching or cross-government fraud detection where data cannot be shared in the clear.
  • Challenge: Balancing linkage accuracy against the information loss introduced by the privacy-preserving encoding.
Bloom Filters
Common PPRL Encoding
IDENTITY RESOLUTION

Frequently Asked Questions

Clear, technical answers to the most common questions about the data management discipline of matching and merging identity records across disparate systems.

Identity resolution is the data management discipline of accurately matching and merging identity data across disparate systems to create a unified, 360-degree view of a customer, patient, or organization. It works by ingesting records from multiple source systems, standardizing and cleansing attributes (names, addresses, emails), applying fuzzy matching algorithms to identify candidate pairs, and using probabilistic record linkage models to calculate match weights. These weights determine whether two records represent the same real-world entity. The process typically involves a blocking step to reduce the computational complexity of pairwise comparisons, followed by a scoring phase using the Fellegi-Sunter model to classify pairs as matches, non-matches, or requiring clerical review. The final output is a persistent canonical entity identifier that links all related records to a single golden record.

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.