A Google Knowledge Graph ID (kg:/m/...) is a unique, machine-generated alphanumeric string assigned by Google's algorithms to a specific entity within its internal Knowledge Graph. Unlike a human-curated Wikidata Q-Node, this identifier is created automatically during Google's entity reconciliation and knowledge extraction processes to serve as a canonical, non-colliding reference for that real-world object, concept, or place.
Glossary
Google Knowledge Graph ID

What is Google Knowledge Graph ID?
A unique machine-generated identifier assigned by Google to every entity in its Knowledge Graph, distinct from human-curated identifiers like Wikidata Q-Nodes.
This identifier acts as the primary key for Google's entity understanding, linking disparate web mentions to a single, unified node. It is distinct from a Canonical URI in linked data but serves a similar purpose for consolidation. Developers encounter these IDs in APIs or knowledge panel URLs, using them for Entity Reconciliation to ensure their structured data, such as JSON-LD Serialization, correctly aligns with Google's understanding of their organization or topic.
Key Characteristics of a Knowledge Graph ID
A Google Knowledge Graph ID (kg:/m/...) is a machine-generated, opaque string that serves as the canonical, immutable identifier for a specific entity within Google's index. Unlike human-readable Q-Nodes, it is algorithmically assigned and optimized for internal graph resolution.
Machine-Generated Opaque String
The ID is an algorithmically assigned alphanumeric string (e.g., /m/0dl567) with no inherent semantic meaning. It is not human-curated or human-readable. Its sole purpose is to act as a unique primary key within Google's massive internal graph database, ensuring that the entity for 'Apple Inc.' is never confused with the fruit.
Distinction from Wikidata Q-Node
A Wikidata Q-Node (e.g., Q312) is a human-curated, open-source identifier from the Wikimedia ecosystem. A Knowledge Graph ID is a proprietary Google construct. While Google often reconciles its IDs against Wikidata using sameAs assertions, the KG ID is the authoritative internal token for Google's own search features, including Knowledge Panels.
The `/g/` vs. `/m/` Prefix
The prefix indicates the source corpus used for entity extraction:
/m/: Derived from Freebase, the original community-curated knowledge base acquired by Google. These represent older, well-established entities./g/: Generated by Google's internal Knowledge Vault algorithms, typically for entities extracted directly from the web that had no prior Freebase entry.
Canonical Entity Resolution
The KG ID functions as the ultimate canonical URI within Google's ecosystem. During entity reconciliation, Google maps all textual mentions, misspellings, and synonymous references to this single ID. This consolidation prevents identity fragmentation and ensures that the 'knowledge panel' aggregates all facts under one authoritative node.
Immutable & Persistent Anchor
Once assigned, a Knowledge Graph ID is effectively permanent. Even if an entity's name changes (rebranding) or its attributes evolve, the ID remains constant. This immutability makes it a reliable semantic anchor for long-term entity linking strategies and ensures historical data integrity within Google's index.
Frequently Asked Questions
Technical answers to common questions about Google Knowledge Graph IDs, their relationship to Wikidata Q-Nodes, and their role in entity disambiguation for generative AI systems.
A Google Knowledge Graph ID (KG ID) is a unique machine-generated alphanumeric identifier, typically formatted as kg:/m/... or /g/..., that Google assigns to every distinct entity within its proprietary Knowledge Graph. Unlike human-curated identifiers, KG IDs are algorithmically created during Google's entity extraction and reconciliation pipelines. The ID serves as a canonical, immutable pointer that disambiguates entities with identical names—for example, distinguishing 'Paris' the city (kg:/m/05qtj) from 'Paris' the mythological figure. When Google's crawlers process web content, they perform entity linking to map textual mentions to these internal IDs, enabling the search engine to build a structured understanding of relationships between people, places, organizations, and concepts. For generative engine optimization, understanding KG IDs is critical because AI-generated overviews and knowledge panels pull directly from this entity index to construct factual, attributed responses.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Core concepts for establishing, linking, and leveraging unique machine-readable identifiers across the knowledge graph ecosystem.
Entity Reconciliation
The computational process of resolving disparate data records to determine if they refer to the same real-world object. This involves probabilistic matching against a canonical knowledge base like Wikidata. Key techniques include:
- Fuzzy string matching on labels and aliases
- Property comparison (birth dates, locations)
- Graph proximity scoring using known relationships Successful reconciliation is the prerequisite for injecting a consistent Google Knowledge Graph ID into enterprise data.
SameAs Assertion
An OWL property (owl:sameAs) used in RDF to explicitly state that two different URIs refer to the identical real-world entity. This is the critical mechanism for cross-source identity resolution. For example, asserting that a DBpedia URI and a Wikidata Q-Node represent the same person. Search engines consume these assertions to consolidate entity profiles and resolve ambiguity.
Canonical URI
A single, authoritative Uniform Resource Identifier designated to represent a specific entity. It prevents identity fragmentation across linked data sources. In enterprise knowledge graph strategy, designating a canonical URI (often a Wikidata Q-Node or a branded HTTP URI) and linking all other representations to it via owl:sameAs is essential for controlling how a brand or entity is represented in generative AI outputs.
Entity Linking
An NLP task that identifies textual mentions of entities and maps them to their unique, unambiguous entries in a target knowledge base. The sub-task of Named Entity Disambiguation resolves ambiguity (e.g., 'Paris' the city vs. 'Paris' the mythological figure). This process is fundamental to how Google extracts entities from web pages and assigns the correct Knowledge Graph ID.
Knowledge Panel Injection
The technical strategy of populating structured data and authoritative sources to influence the information displayed in Google's Knowledge Panel for a specific entity. This relies on:
- Correct entity reconciliation to a known Google Knowledge Graph ID
- Robust JSON-LD serialization with verified property assertions
- Consistent SameAs linking across all owned web properties
- High-confidence entity provenance signals from trusted sources

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us