DefinedTerm is a Schema.org structured data type used to mark up a specific word, name, or phrase alongside its formal definition, typically within a DefinedTermSet or glossary context. It creates an unambiguous, machine-readable link between a term and its meaning, allowing search engines and AI models to resolve semantic ambiguity and build accurate internal knowledge representations.
Glossary
DefinedTerm

What is DefinedTerm?
A structured data type for explicitly linking a word or phrase to its authoritative definition, enabling AI systems to build precise, disambiguated internal glossaries.
The type uses properties like termCode for unique identifiers and inDefinedTermSet to specify the governing vocabulary. By implementing DefinedTerm, organizations provide entity disambiguation signals that prevent AI models from confusing industry-specific jargon with common language, directly improving the factual grounding of generative engine outputs.
Key Properties of DefinedTerm
The DefinedTerm type is a structured way to mark up a word, name, or phrase alongside its formal definition. It is a critical component for building machine-readable glossaries, dictionaries, and knowledge bases that AI-driven search engines can parse with high precision.
Core Definitional Structure
The primary purpose of DefinedTerm is to create an unambiguous link between a term and its definition. This is achieved through two essential properties:
name: The word, phrase, or acronym being defined (e.g., "API").description: The formal, concise definition of the term. This pairing allows search engines to extract exact definitions for featured snippets and AI-generated overviews, rather than inferring meaning from surrounding text.
Entity Disambiguation with `termCode`
To resolve ambiguity, DefinedTerm supports the termCode property. This allows you to link the term to an external, canonical identifier from an established controlled vocabulary.
- Mechanism: The value is typically a short, unique code (e.g.,
MS-100). - Context: Used in conjunction with
inDefinedTermSet, which points to theDefinedTermSet(the glossary or dictionary) that defines the code. This is crucial for enterprise knowledge graphs where a single term like "vector" might have different meanings in mathematics versus machine learning.
Contextual Containment via `inDefinedTermSet`
A DefinedTerm does not exist in isolation. The inDefinedTermSet property explicitly links the term back to its parent glossary or dictionary, represented by a DefinedTermSet type.
- Purpose: This establishes the provenance and scope of the definition.
- Benefit: It tells an AI parser, "This definition is valid within this specific context," preventing the misapplication of a domain-specific definition to a general query. This relationship is fundamental for building a connected, semantic web of organizational knowledge.
Practical JSON-LD Implementation
Implementing DefinedTerm in JSON-LD is straightforward and nests cleanly within a DefinedTermSet. A minimal example:
json{ "@context": "https://schema.org", "@type": "DefinedTermSet", "name": "AI Glossary", "hasDefinedTerm": { "@type": "DefinedTerm", "name": "Large Language Model", "description": "A type of AI model trained on vast text data to generate and understand human language.", "termCode": "LLM-001" } }
This explicit structure is far more parseable for generative engines than a standard HTML definition list.
Relationship to `DefinedTermSet`
DefinedTerm is the individual entry, while DefinedTermSet is the container—the glossary or codebook itself. The relationship is established via the hasDefinedTerm property on the DefinedTermSet, which takes an array of DefinedTerm objects.
- Analogy: Think of
DefinedTermSetas the dictionary book andDefinedTermas each individual entry within it. - SEO Impact: This parent-child relationship signals to crawlers that a page is a comprehensive, authoritative source on a cluster of related concepts, boosting its entity salience for an entire topic area.
Advanced Attribution with `url`
For maximum authority and citation integrity, use the url property on a DefinedTerm to point directly to the canonical web page that elaborates on the definition.
- Function: This provides a machine-readable citation link.
- Strategic Use: When an AI model generates an answer using your definition, this URL serves as a strong signal for attribution. It directly connects the concise
descriptionin the markup to the long-form, authoritative content on your site, reinforcing your position as the primary source.
Frequently Asked Questions
Clarifying the technical implementation and strategic value of the DefinedTerm schema type for AI-driven search and knowledge graph construction.
The DefinedTerm type is a Schema.org structured data class used to explicitly mark up a word, name, or phrase alongside its formal definition within a web document. It functions by creating a semantic link between a name (the term) and a description (the definition), often nested within a parent DefinedTermSet or a Glossary page. When implemented via JSON-LD, it signals to AI parsers and search engine crawlers that a specific text span is not just a string, but a formally defined concept. This allows generative engines to disambiguate jargon, extract precise definitions for featured snippets, and populate knowledge graph nodes with authoritative, structured explanations rather than relying on probabilistic inference from unstructured text.
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
Understanding DefinedTerm requires familiarity with the broader Schema.org vocabulary and the mechanisms that enable AI-driven search engines to parse and disambiguate definitions within a knowledge graph.
Entity Linking via @id
To prevent ambiguity, a DefinedTerm should be assigned a globally unique Internationalized Resource Identifier (IRI) using the @id keyword. This transforms the term from a simple string into a distinct, referenceable node that can be linked to external authority sources like Wikidata using the sameAs property.
Glossary Container Strategy
A DefinedTerm is rarely used in isolation. It is typically nested within a DefinedTermSet or a parent ItemList. This hierarchical structure signals to generative engines that the page is a definitive glossary, increasing the likelihood of the AI citing the definition directly in an answer engine overview.
Speakable Selection
For voice assistant optimization, the speakable property can be applied to the description of a DefinedTerm. This explicitly instructs text-to-speech engines to read the definition aloud in response to 'What is X?' queries, bypassing verbose page content to deliver a concise audio snippet.
MainEntity Disambiguation
On a dedicated glossary page, the primary DefinedTerm should be declared as the mainEntity of the WebPage. This explicit signal resolves page-level ambiguity for AI parsers, confirming that the specific term—and not the site navigation or footer—is the central topic of the content.
TermCode for Machine Readability
The termCode property allows you to associate a DefinedTerm with a machine-readable identifier from an external coding system. For example, linking a technical term to its specific Wikidata Q-ID or an internal enterprise taxonomy code ensures deterministic matching across heterogeneous data systems.

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