Entity Disambiguation
Session 1.7 · ~5 min read
If your company is called "Maju Bersama," you have a problem. There are likely hundreds of businesses in Indonesia with that name. Google sees "Maju Bersama" across multiple websites, directories, and profiles, and it cannot tell which references belong to your company and which belong to others. This is the disambiguation problem.
Disambiguation is the process by which Google determines which entity a reference points to. When the name alone is ambiguous, Google uses context signals to resolve the ambiguity. If those signals are weak or absent, Google either picks the wrong entity, splits your signals across multiple entities, or simply ignores the reference.
How Google Disambiguates
Google uses several types of context to disambiguate entities:
'Maju Bersama'"] --> L["Location Context
Jakarta vs. Surabaya"] N --> I["Industry Context
Construction vs. Catering"] N --> P["People Context
Different founders"] N --> U["URL Context
Different domains"] N --> S["Structured Data
Different schema declarations"] L --> R["Resolved Entity"] I --> R P --> R U --> R S --> R style N fill:#2a2a28,stroke:#c47a5a,color:#ede9e3 style R fill:#2a2a28,stroke:#6b8f71,color:#ede9e3 style L fill:#2a2a28,stroke:#c8a882,color:#ede9e3 style I fill:#2a2a28,stroke:#c8a882,color:#ede9e3 style P fill:#2a2a28,stroke:#c8a882,color:#ede9e3 style U fill:#2a2a28,stroke:#c8a882,color:#ede9e3 style S fill:#2a2a28,stroke:#c8a882,color:#ede9e3
Each context signal narrows the possibilities. "Maju Bersama" is ambiguous. "Maju Bersama, Jakarta, construction" narrows it significantly. "Maju Bersama, Jl. Sudirman 45, Jakarta, construction, founded 2005 by Ahmad Pratama, website majubersama.co.id" is probably unique.
Disambiguation is not optional. If Google cannot tell your entity apart from others with the same name, your signals get diluted or attributed to the wrong entity.
Disambiguation Signals Ranked
| Signal | Disambiguation Power | Where to Implement |
|---|---|---|
| Unique website URL | Very High | Schema.org url property |
| Wikidata Q-identifier | Very High | Wikidata entry, sameAs link |
| Physical address | High | Schema, GBP, citations |
| Phone number | High | Schema, GBP, citations |
| Industry/category | Medium-High | Schema description, GBP category |
| Founding date | Medium | Schema, Wikidata, About page |
| Founder name | Medium | Schema founder property, About page |
| Social profile URLs | Medium | Schema sameAs array |
| Logo | Medium | Schema logo property, GBP |
| Legal registration number | High | Government databases, Wikidata |
The strongest disambiguation signal is a unique URL. No two entities share the same website domain. If your Organization schema declares your URL, and your GBP, social profiles, and citations all point to the same URL, Google has a strong anchor for your entity.
The Name Collision Problem
Some businesses face severe name collisions. If your company name is "Global Technology Solutions," you are competing with hundreds of entities for that name string. Google's disambiguation system will default to the entity with the strongest signals, which is usually the largest or most established one.
For businesses with common names, entity infrastructure is not optional. It is survival. Without strong disambiguation signals, your entity signals get absorbed by a larger entity or scattered across multiple unresolved references.
Strategies for Ambiguous Names
If your company name is common, you have several options:
- Add a geographic qualifier in your structured data and GBP: "Global Technology Solutions Jakarta" (but keep the legal name accurate).
- Strengthen the URL signal: Make sure every reference to your company includes your website URL.
- Build sameAs connections: Link your website schema to your LinkedIn, Facebook, Wikidata, and every other profile. These create a web of corroborating identifiers.
- Emphasize unique properties: Founding date + founder name + industry + location creates a unique combination even when the name is generic.
- Create a Wikidata entry: The Wikidata Q-identifier is a unique, permanent entity ID that Google trusts for disambiguation.
If your company name is unique, you have a natural advantage. Protect it by maintaining consistent usage everywhere. Never abbreviate, never vary the format, and never use a different name on any platform.
Further Reading
- Google Knowledge Graph Reconciliation - Bill Slawski on how Google resolves entity references across sources
- Evolution of a Knowledge Panel - Kalicube case study showing how disambiguation signals trigger Knowledge Panel creation
- Google Patent Analysis: Entities in Queries - How Google processes entity disambiguation in search queries
Assignment
Google your company name. Count how many different companies or organizations share that name in the results. If more than one exists, list 5 signals that could help Google tell yours apart from the others: your URL, your city, your industry, your founder, your founding date. If your name is unique, document why that is an advantage and make sure you never use variations of it.