wikidata-presence

What this datapoint measures

Whether the brand exists in Wikidata as a sourced, identified entity with substantive properties. Wikidata is Wikipedia’s structured-data sibling and one of the most consequential structured-knowledge systems for AI grounding.

What high looks like

• Wikidata Q-number entity exists for the brand
• Major identifying properties present and source-cited (founding date, country, official website, business activity, key personnel, industry classification)
• sameAs identifiers connecting to external authoritative systems where applicable
• Aliases declared (alternate name forms across languages)
• Recent activity in the entity’s edit history (active maintenance)

What low looks like

• Wikidata entity exists but with sparse properties
• Properties asserted without source citations
• Identifiers limited
• Edit history shows the entity is dormant

What at floor looks like

A brand at floor on wikidata-presence has no Wikidata entity, or has an entity that is at risk of deletion (insufficient sourcing, contested by editors). The brand is not registered in the structured-knowledge system that AI training corpora and retrieval pipelines extensively use.

This is universal at AS ≈ 0 and persists until G-1 (Entity Verification) and G-11 (Wikipedia and Wikidata Optimization) work has been substantively completed. The remedy is direct: execute G-11.

What affects this datapoint

• Wikidata entity existence
• Property completeness
• Source citation per property
• sameAs identifier coverage
• Edit-history activity
• Cross-language label coverage

OMG actions that influence this datapoint

Action	Influence
G-11 Wikipedia & Wikidata Optimization	Direct, primary. wikidata-presence is the primary measurement of G-11 outcomes.
G-1 External Entity Verification, Knowledge Graph & Local Authority	Direct. G-1 establishes entity foundations that flow into Wikidata work.

Multilingual considerations

Wikidata is multilingual at its core; entities have labels and descriptions in many languages. Considerations:

• Per-language labels should be canonical for each language (Japanese-script label for ja-language; romanization in alias)
• Cross-language sameAs links to per-language Wikipedia articles where they exist
• Property values may be language-neutral (numbers, dates) or language-specific (descriptions)

Common failure modes

• Wikidata entity created without source citations; gets challenged or deleted
• Entity properties from auto-import without verification
• Entity referencing a parent corporation rather than the specific brand
• Entity not maintained, drifting out of date as brand changes

Diagnostic interpretation

wikidata-presence at floor is the universal starting state for foundations and depth-stage brands. G-11 work is the path forward, with G-1 prerequisites to be in place first.

wikidata-presence at low with knowledge-graph-depth (next datapoint) also low indicates G-11 work has begun but is incomplete. The remedy is to complete the G-11 phases.

wikidata-presence at high with knowledge-graph-depth at low indicates Wikidata-specific success without broader knowledge-graph presence. Wikidata is one node; broader work (other knowledge graphs, business directories, industry registries) is needed for full V3.1 lift.

---