Entity Resolution
Entity resolution is identifying and linking records that refer to the same real-world entity (person, firm, or asset) across sources.
Allocator relevance: Prevents broken profiles and enables accurate network mapping, coverage metrics, and decision-maker identification.
Expanded Definition
Allocator data is messy: spelling variants, legal entities, SPVs, holding companies, and role changes create fragmented records. Entity resolution connects these fragments into a coherent identity graph while preserving evidence and confidence levels. It is broader than deduplication: it can link related entities (e.g., firm ↔ subsidiaries ↔ SPVs) even when they are not exact duplicates.
For Altss, entity resolution is fundamental to mapping households, beneficial ownership, and decision chains.
How It Works in Practice
Systems use identifiers (domains, filings, addresses, LinkedIn IDs), similarity signals, and relationship patterns to link entities. Outputs should include confidence scoring, data lineage, and human review workflows for high-impact merges.
Decision Authority and Governance
Governance defines linking thresholds, audit trails, and correction pathways. Incorrect entity resolution can be worse than duplicates because it creates false associations—especially for beneficial ownership and contact mapping.
Common Misconceptions
- Entity resolution is solved once and stays solved.
- Aggressive linking always improves coverage.
- Resolution is the same as deduplication.
Key Takeaways
- Entity resolution improves trust and usability across the product.
- Confidence scoring and lineage are mandatory.
- Mistakes can create reputational risk; governance matters.