Glossary

Thing

The most generic, top-level class in the Schema.org hierarchy from which all other specific types, such as CreativeWork or Event, are derived.

Get in touch Learn more

Knowledge engineer constructing knowledge base on laptop, document hierarchy visible, casual office setup.

SCHEMA.ORG FOUNDATIONAL CLASS

What is Thing?

The most generic, top-level class in the Schema.org hierarchy from which all other specific types, such as CreativeWork or Event, are derived.

Thing is the universal superclass in the Schema.org vocabulary, serving as the abstract root from which every other defined type—including Person, Place, Organization, and CreativeWork—inherits its fundamental properties. It represents the broadest possible entity, encompassing both tangible objects and intangible concepts, and provides the minimal set of attributes like name, description, and url that are common to all structured data markup.

In JSON-LD serialization, Thing is rarely instantiated directly; instead, it acts as the conceptual anchor for the entire type hierarchy. Its core properties, particularly @id and sameAs, are critical for entity linking and knowledge graph injection, enabling developers to establish unambiguous identity and equivalence relationships across disparate data sources for AI-driven search engines.

SCHEMA.ORG FOUNDATION

Key Properties of Thing

The Thing class is the universal supertype in Schema.org, providing the foundational properties inherited by every other type. Understanding these core attributes is essential for constructing valid, interconnected knowledge graphs.

Universal Identifier (@id)

The @id property assigns a globally unique Internationalized Resource Identifier (IRI) to a node. This is the single most critical property for entity reconciliation and linking.

Enables unambiguous reference from other nodes
Prevents entity duplication in a Graph context
Essential for connecting your local entity to external authorities via sameAs

Example: "@id": "https://example.com/entity#company"

Type Declaration (@type)

The @type property specifies the class of the entity, moving it from an abstract concept to a concrete definition.

Accepts a single string or an array for multiple inheritance
Drives eligibility for search engine rich results
Common values: Organization, Product, Event, CreativeWork

Example: "@type": ["Organization", "Corporation"]

Semantic Naming (name)

The name property provides the primary, human-readable label for the entity. This is distinct from an alternateName or a legal name.

Used by AI models for entity salience and disambiguation
Should match the most common public-facing brand string
Avoid keyword stuffing; use the exact brand name

Example: "name": "Inferensys"

Entity Description (description)

The description property provides a concise textual summary of the entity. This field is heavily weighted by generative engines for summarization.

Use natural, declarative language
Include core attributes and primary function
Acts as a direct signal for answer engine optimization

Example: "description": "A global technology consultancy specializing in enterprise AI architecture."

Visual Identity (image)

The image property links to a visual representation of the entity, typically a logo or photograph.

Must point to a crawlable, high-resolution URL
Google requires images to be in a supported format (JPEG, PNG, WebP)
Critical for brand entity optimization in knowledge panels

Example: "image": "https://example.com/logo.png"

Web Presence (url)

The url property points to the canonical, authoritative homepage or web address for the entity.

Must exactly match the canonical URL of the page
Used to resolve the mainEntity of a page
Establishes the primary digital location for the entity

Example: "url": "https://www.example.com"

SCHEMA.ORG FUNDAMENTALS

Frequently Asked Questions

Clear, technically precise answers to the most common questions about the Schema.org Thing class and its role in structured data hierarchies.

The Thing type is the most generic, top-level class in the Schema.org hierarchy from which all other specific types—such as CreativeWork, Event, Organization, or Person—are derived. It serves as the universal parent class, providing the foundational properties that every entity in a structured data graph inherits. These core properties include name, description, url, image, and sameAs. Because every more specific type is a descendant of Thing, parsers and search engines can reliably fall back to these base properties when encountering an unfamiliar or custom type. This extensibility is critical for Generative Engine Optimization, as it ensures that even novel or niche entities remain parsable by AI-driven search overviews and knowledge graphs. When defining a custom entity that lacks a precise existing Schema.org type, using Thing with robust @id and sameAs linking is the safest way to maintain semantic integrity.

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.

Enterprise searchRAGPermissions

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.

AI agentsWorkflow automationGovernance

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.

AI integrationDecision supportModel routing

SCHEMA.ORG HIERARCHY

Related Terms

Understanding the Thing class requires familiarity with the foundational concepts that extend, identify, and contextualize it within the Schema.org ecosystem.

@type

The fundamental Schema.org property that assigns a specific class to an entity. When you declare "@type": "Thing", you are explicitly stating that the subject is the most generic entity possible. In practice, @type is almost always set to a more specific descendant like CreativeWork or Organization to enable richer semantic parsing. The property is mandatory for all Schema.org markup and serves as the primary disambiguation signal for search engines.

EXPLORE

@id

A JSON-LD keyword that assigns a globally unique Internationalized Resource Identifier (IRI) to a Thing instance. Using @id transforms an anonymous node into a referenceable entity, enabling other nodes to link to it via properties like subjectOf or mainEntity. This is the foundational mechanism for constructing interconnected knowledge graphs where a single Thing can be referenced from multiple pages without data duplication.

SameAs Property

A Schema.org property on Thing that establishes an equivalence relationship between the current entity and its canonical representations on external authoritative knowledge bases. Common targets include:

Wikidata entries (e.g., https://www.wikidata.org/wiki/Q42)
Wikipedia pages
DBpedia URIs This property is critical for entity reconciliation, helping AI models merge information about the same real-world object from disparate sources.

Entity Linking

The computational process of identifying textual mentions of a Thing within unstructured content and disambiguating them by connecting each mention to a unique, canonical entry in a knowledge base. For example, distinguishing whether the word "Apple" refers to the Organization (the company) or the Product (the fruit). Effective entity linking is a prerequisite for building accurate knowledge graphs and improving AI citation fidelity.

MainEntity

A Schema.org property used to explicitly indicate the primary Thing described on a web page. When a page contains multiple entities, mainEntity resolves ambiguity by telling parsers which subject is the central focus. This is particularly important for AI-driven summarization, where the model must identify the dominant topic to generate an accurate overview rather than being distracted by secondary entities.

Graph

A top-level JSON-LD construct that encapsulates multiple interconnected Thing nodes within a single structured data block. Using @graph allows you to define several entities and their relationships simultaneously without repeating shared identifiers. This is the preferred pattern for representing complex pages where a WebPage, an Organization, and a Product all need to be defined and linked together.

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.

Limited slotsGet a Free AI Consultation

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.