Skip to main content

Contact

What are you interested in?

Back to Glossary (S)
Glossary · S

Semantic Triple.

A semantic triple is the smallest unit of machine-readable knowledge and consists of subject, predicate and object — for example 'DLM Digital – has location – Zollikon'. Knowledge graphs and AI systems store facts in exactly this three-part form.

SEGLOSSARYDLM Digital

Semantic Triple — Explained in Detail

A semantic triple describes a fact in three parts: subject, predicate, object. 'Zollikon – lies in the canton of – Zurich' is one triple; 'DLM Digital – offers – Local SEO' is another. People read this as a sentence, machines as a record. The advantage of the breakdown is that millions of such statements can be joined into a network without contradiction. That is precisely what knowledge graphs such as Google's Knowledge Graph or Wikidata consist of: not running text, but relationships between unambiguously identified things.

The move from text to triples is where SEO turns technical. When a page says 'We are a digital agency in Zollikon looking after SMEs across the Zurich region', a machine first has to extract entities and relationships from that sentence, with a corresponding risk of error. If the same facts are additionally marked up as JSON-LD, they already exist as triples: Organization, address, Zollikon. Structured data is nothing other than pre-formulated triples that spare the machine the interpretation work and prevent misreadings.

For AI search this is more than technical hygiene. A language model answering 'which agencies in Zollikon do GEO?' is effectively running a query over relationships: find every entity of type organisation with location Zollikon and service GEO. A company whose facts exist cleanly as triples, and agree across several sources, is findable in that query. A company that keeps the same facts only in running text and images has to hope the automatic extraction happens to work correctly.

A concrete case: a trade business was assigned to the wrong town by assistants, because the billing address in one directory and the workshop address on the website diverged. Read as triples, two contradictory statements about the same subject simply existed side by side. The fix was not more content but unambiguity: a single address, marked up in LocalBusiness schema, plus sameAs references to the official profiles and a correction of the divergent directory entry. After that the network held only one statement about the location, and the attribution was right in maps and in AI answers alike.

Related Page

Knowledge Graph

Frequently Asked Questions About Semantic Triple

Schema.org supplies the vocabulary for the predicates. When you use 'address' or 'areaServed' in JSON-LD, you are naming the relationship between your company as subject and a place as object. The value of a standardised vocabulary is that every search engine and every model interprets the same predicates in the same way. Without a standard, each machine would have to guess whether 'seat', 'location' and 'address' mean the same thing.

Usually not directly. You write JSON-LD, and the search engine translates it into triples internally. What matters is the editorial side: every core statement about your company should have exactly one unambiguous form and be identical across your website, your Google Business Profile and the directories. Contradictions almost never arise from missing markup — they arise from two different answers to the same question.

Ready for Your Project?

Apply this knowledge to your website — DLM Digital will help you.