knowledge-graph-depth

What this datapoint measures

Richness of the brand’s representation across knowledge-graph systems beyond Wikidata. Including Google Knowledge Graph, schema-driven knowledge systems, business registries, industry databases, and similar structured-knowledge platforms that AI systems consult.

What high looks like

• Brand entity present and substantive in multiple knowledge-graph systems
• Properties consistent across systems (same founding date, same address, same key personnel)
• sameAs links cross-referencing the entity across systems
• Industry-specific knowledge graphs include the brand where applicable
• Verified business listings (Google Business Profile, equivalent regional services)

What low looks like

• Brand entity in one knowledge-graph system but not others
• Properties inconsistent across systems (different addresses, different founding dates)
• No cross-references between systems
• Industry-specific knowledge graphs missing the brand

What at floor looks like

A brand at floor on knowledge-graph-depth has minimal or no presence across structured-knowledge systems. Wikidata may or may not exist, but other structured-knowledge sources do not represent the brand. The brand’s entity grounding for AI systems comes only from its own self-declared structured data, which is the most easily-questioned source.

The remedy is G-1 (Entity Verification) work executed comprehensively, including knowledge-graph presence beyond Wikidata. This is multi-track: business directories, industry-specific registries, regional knowledge systems where applicable.

What affects this datapoint

• Presence across multiple knowledge-graph systems
• Property consistency across systems
• sameAs cross-references
• Industry-specific knowledge-graph presence
• Verified business listings

OMG actions that influence this datapoint

Action	Influence
G-1 External Entity Verification, Knowledge Graph & Local Authority	Direct, primary. G-1 work explicitly builds knowledge-graph depth.
G-11 Wikipedia & Wikidata Optimization	Substantial. Wikidata is one component; G-11 contributes to the broader depth.
O-7 Compliance & Trust Infrastructure	Indirect. Compliance work sometimes surfaces business-registry obligations that contribute to knowledge-graph depth.

Multilingual considerations

Knowledge-graph systems vary by region and language:

• Google Knowledge Graph operates internationally but with regional variation
• Regional business registries are language- and country-specific (Indonesia’s KBLI, Japan’s company registries, Taiwan’s MOEAIC)
• Industry-specific knowledge graphs may be language-specific
• Per-language Wikipedia articles populate per-language knowledge subgraphs

A brand operating in multiple languages should expect knowledge-graph-depth to lift independently per language and per region. The work in Indonesia is not the work in Japan.

Common failure modes

• Wikidata presence achieved but no other knowledge-graph work attempted
• Business registry information out of date or inconsistent with other declarations
• Industry-specific knowledge graphs ignored (the brand exists in Google’s broad knowledge graph but is missing from sector-specific systems)
• Different brand information across systems creating contradictions that AI systems detect

Diagnostic interpretation

knowledge-graph-depth at floor is the universal starting state. G-1 work is the systemic remedy.

knowledge-graph-depth at low with wikidata-presence at high indicates Wikidata success without broader G-1 work. The remedy is to expand G-1 beyond Wikidata.

knowledge-graph-depth at high with content-depth (V2.1) at low indicates structured-knowledge presence without underlying content. The brand’s entity is well-represented but the content the entity points to is thin. M-pillar work is the remedy.

---