How does Five Blocks handle reputation management for individuals with common names?

Common-name reputation work is a specialty inside the broader executive practice because the failure modes are distinctive. A client named John Smith, Sarah Chen, or Michael Cohen will be conflated with namesakes by both Google and AI engines unless explicit disambiguation infrastructure is built at the entity layer.

Research confirms the underlying risk: large language models have been shown to mishandle broad classes of human names even in short text due to ambiguous linguistic cues, and weak entity infrastructure, no Wikidata entry, no schema markup, no clean disambiguation, makes conflation significantly more likely.

The disambiguation infrastructure

1. Wikidata entity record

   Five Blocks creates or completes a distinct Wikidata item for the client with full disambiguating attributes: date of birth, current employer, prior employers, and notable affiliations. Each item carries a unique Q-identifier that machines can use to distinguish this person from any namesake. Where a Wikipedia article exists, it is linked as a sitelink on the same item.

2. Owned bio page with schema.org Person markup

   The client’s bio page on the company site is marked up with schema.org/Person and carries sameAs links pointing to the Wikidata Q-item, LinkedIn profile, Wikipedia article (where applicable), and any other authoritative identifiers. Schema.org defines sameAs as “URL of a reference Web page that unambiguously indicates the item’s identity”, exactly the disambiguation signal engines need. This page becomes an anchor in the client’s identity graph.

3. Third-party citations with disambiguating context

   Third-party coverage, press mentions, bylined articles, industry profiles, is encouraged toward sources that consistently use the client’s disambiguating context (title, employer, credential) alongside the name. Each citation that does so reinforces the engine’s routing confidence.

4. Wikipedia (where notability supports it)

   Where the client meets Wikipedia’s notability threshold, a Wikipedia article provides the strongest single disambiguation signal available. Wikipedia’s own disambiguation system uses dedicated disambiguation pages and unique identifiers to resolve conflicts between subjects who share a name. An article linked to the Wikidata item ties all layers together.

The compound effect

The combined effect is that search engines and AI engines start routing the client’s queries to the client rather than to a namesake. Person schema with verified sameAs links helps engines build an identity graph and provides biographical disambiguation anchors. The disambiguation strengthens over time as the entity signals deepen and more citations adopt the consistent context.