Knowledge Graph Presence

1. What knowledge graph presence is

Definition (GEO Wiki working definition): knowledge graph presence, as a GEO signal, is the existence — and accuracy, and claimed status — of a structured entity node for you (a Wikipedia article, a Wikidata Q-item, a Google Knowledge Graph / Knowledge Panel entry) inside a graph an AI engine already trusts.

This entry is not a Wikipedia or Wikidata how-to, and it is not the resolution mechanism — Entity Recognition owns the matching layer that joins a mention to a node. The narrower question here is whether a trusted node exists for you to be matched to and amplified by.

2. Why a node amplifies but does not cause — the load-bearing honesty

This entry’s counterpart to Entity Recognition §6’s “resolution is corroborated, not asserted”, Brand Mentions §5’s “a link with no mention is not a completed authority play”, Schema.org for AI’s “declared, not rewarded”, and E-E-A-T §6’s “earned, not annotated”: a node is an amplifier, not a cause — presence raises the prior and gives resolution a destination; it does not itself get a passage cited, and it cannot be self-declared into existence.

The amplifier is a double-dip — the node is consumed at two points, not one:

   off-site notability / mentions   ◄── earned: Brand Mentions
            │
            ▼
   [ STRUCTURED NODE ]   ◄── this entry
   Wikipedia · Wikidata · Google KG
      │                       │
      ▼ (training time)       ▼ (retrieval / grounding time)
   stronger model prior    KG-/Wikidata-backed
   (Wikipedia in the         disambiguation + recall
   pretraining corpus)       amplifier on index surfaces
      └──────────┬───────────┘
                 ▼
   amplified — but the passage still must be
   liftable (Citability) and trusted (E-E-A-T)

Where it acts is the point. The node is standing infrastructure, not a runtime decision: it shapes the prior at training time and backs disambiguation at retrieval time, both upstream of the Answer Loop §3 grounding/selection gate that Citability and E-E-A-T govern. The node does not pick the passage.

Three orthogonality lines, stated so they cannot be misread:

• Presence ≠ liftability. Making a passage quotable is Citability’s.
• Presence ≠ trust. Whether the node is a trusted authority is E-E-A-T’s.
• Presence ≠ resolution. Being matched to the node from your mentions is Entity Recognition’s; the node existing is here — the exact reciprocal of Entity Recognition §2’s third orthogonality line.

3. The mechanism — the three layers and how they feed each other

Knowledge graph presence is not one thing. It is three nodes in three graphs with different permeability, feeding each other in one direction. This layered model is the part the siblings deliberately do not carry — it is this entry’s core.

The feed direction — the node is the middle amplifier, never the origin:

  off-site notability ─► Wikipedia ─► (pretraining prior)
             │               └─────►┐
             └─► Wikidata ──────────┼─► Google KG ─► Google AI surfaces
                                     (sameAs destination)

The join key ties back to Schema in one line. sameAs is the explicit edge into this graph. Which markup carries sameAs is in Schema.org for AI §4; what it points to — the node — is below. For the JSON-LD block, see Schema.org for AI or the Schema Implementation playbook. In prose, sameAs simply asserts “the entity at this page is the one at wikidata.org/wiki/Q…,” and the destination of that assertion — a trusted node — is what this entry is about.

4. The levers — what makes a node exist and count (concept, not runbook)

A concept-level taxonomy of presence levers, each tagged with the §3 layer it builds. This is not a runbook — the doing (earn notability, file the item, claim the panel, point sameAs) is the Schema Implementation playbook’s, plus the stated notability-runbook gap (§8).

The line that ties it back, the mirror of Entity Recognition §4’s “you do not declare an identity”: you do not mint a node — you become eligible for one by being notable off-site; presence is downstream of earned attestation. Trust framing of the node is E-E-A-T’s axis.

5. How presence cashes out by surface (invariant vs delta)

The amplifier mechanism (§2/§3) is invariant — it holds everywhere. What varies is which layer a surface reads.

The over-citation is measured, not folkloric: one 2025 citation-pattern analysis found Wikipedia was ChatGPT’s single most-cited source at ~7.8% of all citations (Profound, AI Platform Citation Patterns) — a vendor analytics figure, read for direction, not as a coefficient.

One routed line, not expanded: the same entity needing a node per language (zh Wikipedia/Wikidata vs en) is not derived here — that is Multilingual GEO’s.

6. What the evidence says — and what it does not

The amplifier direction is well-attested; the brand-level dose-response is not. Read this table the way the site reads Aggarwal — for direction, not a coefficient.

Honest gap: Generative Engine Optimization’s headline lever — Aggarwal et al. (KDD ‘24, arXiv:2311.09735; paper summary) — measured on-page content rewrites (cite sources, add statistics, quotations), not knowledge-graph presence. The up-to-40% figure does not transfer to “get a Wikipedia page.” Borrowing it here would be the exact over-claim the siblings warn against.

The position, the reciprocal of Entity Recognition §6’s “corroborated, not asserted” and E-E-A-T §6’s “earned, not annotated”: presence is earned through notability, not minted — a node you created with no independent attestation is not presence; it is a claim.

7. Anti-patterns — minted nodes and false joins

The errors this entry exists to prevent — mirror of Entity Recognition §7, Brand Mentions §8, and Schema.org for AI §7.

The load-bearing line: the node is the destination, not the journey — you become eligible for one by being notable off-site, not by minting one; a self-minted node is an unbacked claim.

8. Why this matters for GEO + how to act

Knowledge graph presence is the standing amplifier under the entity — it strengthens the prior and gives resolution somewhere to land. Pair it with the off-site signal that earns it (Brand Mentions), the resolution that uses it (Entity Recognition), and the markup that points to it (Schema.org for AI). This entry is the concept; the doing is the playbook — with one honest gap: the sameAs join routes to Schema Implementation, but there is no notability/Wikipedia runbook yet, so this entry states that rather than link a page that does not exist.

References

Academic:

• Kandpal, N., Deng, H., Roberts, A., Wallace, E. & Raffel, C. (2023). Large Language Models Struggle to Learn Long-Tail Knowledge. ICML 2023 (PMLR v202). arXiv:2211.08411
• Mallen, A., Asai, A., Zhong, V., Das, R., Khashabi, D. & Hajishirzi, H. (2023). When Not to Trust Language Models: Investigating Effectiveness of Parametric and Non-Parametric Memories. ACL 2023. ACL Anthology · arXiv:2212.10511
• Aggarwal, P. et al. (2024). GEO: Generative Engine Optimization. KDD ‘24. arXiv:2311.09735 · paper summary — boundary reference; knowledge-graph presence is not a tested variable

Official:

• Google — Introducing the Knowledge Graph: things, not strings (2012-05-16) — the “entities, not strings” model
• Google Knowledge Panel Help — Get verified on Google — claiming a knowledge panel
• Google Search Central — Organization structured data — sameAs “used behind the scenes to disambiguate your organization from other organizations”
• Schema.org — sameAs — “URL of a reference Web page that unambiguously indicates the item’s identity”

Policy:

• Wikipedia — Notability — “presumed … suitable … when it has received significant coverage in reliable sources that are independent of the subject”
• Wikipedia — Paid-contribution disclosure — paid editing must be disclosed
• Wikidata — Notability — items need a “clearly identifiable conceptual or material entity … described using serious and publicly available references”

Industry:

• Profound — AI Platform Citation Patterns (2025-06-05) — Wikipedia as ChatGPT’s most-cited source (~7.8%); read for direction, vendor-measured