Identity Disambiguation
Distinguishing between entities or people with similar names by confirming unique identifiers and relationship patterns.
Prevents false matches that waste outreach on wrong targets or worse, embarrassing contact with incorrect person claiming to be decision-maker.
Expanded Definition
Disambiguation combines multiple identifiers to confirm uniqueness: legal entity name + jurisdiction, founding date, known affiliates, addresses, email domains, phone area codes, and relationship networks. Common disambiguation scenarios: common surnames (John Smith), generic company names (Summit Capital), multiple funds with similar names (ABC Partners I, II, III), and family office name variants.
Disambiguation becomes critical when: outreach ROI is high (large potential commitment), relationship damage is costly (embarrassing errors with gatekeepers), or compliance requires certainty (KYC/AML verification). Low-stakes situations (preliminary research, broad market mapping) tolerate disambiguation ambiguity.
Signals & Evidence
Disambiguation indicators:
- Unique identifiers: Legal entity name + jurisdiction, EIN/tax ID, SEC CIK number, regulatory registration numbers
- Relationship patterns: Known affiliates, co-investors, service providers, address history
- Temporal markers: Founding date, fund vintage years, transaction dates
- Contact patterns: Email domains, phone area codes, LinkedIn employer history
- Cross-reference validation: Multiple databases listing same entity with consistent identifiers
Decision Framework
- Disambiguation rigor: High-stakes outreach requires strong disambiguation (3+ unique identifiers); low-stakes research accepts weaker disambiguation
- Conflict investigation: When identifiers disagree (same name, different addresses), investigate for: name reuse, entity splits, or data errors
- False match prevention: Always confirm at least 2 unique identifiers before high-stakes contact
Common Misconceptions
"Name match = same entity" → Common names create frequent false matches; always verify with additional identifiers. "LinkedIn confirms identity" → Multiple people share names and employers; cross-check email, location, role details. "Disambiguation is one-time" → Entities evolve (name changes, mergers, relocations); re-verify periodically.
Key Takeaways
- Identity disambiguation requires multiple unique identifiers (name + jurisdiction + founding date + affiliates), not just name matching
- Prioritize disambiguation rigor for high-stakes outreach to prevent costly errors
- Conflicts between identifiers signal investigation needs (entity splits, name reuse, data errors), not data discarding