Skip to main content
A triple is the smallest piece of information stored in a World. In other literature, it may occasionally be referred to as a “triplet” or “tuple,” but Worlds standardizes on “triple.” Every fact is expressed as three components:
ComponentRoleExample
SubjectThe item being describeduser:ethan
PredicateThe relationship or propertyschema:worksAt
ObjectThe target value or itemorg:wazoo
Together they read as a single statement: Ethan works at Wazoo.

​
Anatomy of a triple

Anatomy of an RDF triple A triple statement is built from fundamental components called RDF Terms. There are two primary types of nodes that make up these terms:
  • Named nodes (URIs/IRIs): Unique identifiers that point to specific, global items or properties. Subjects and Predicates must always be named nodes, allowing them to explicitly link to other parts of the graph.
  • Literal nodes (Values): Raw data values, such as strings, numbers, or dates (e.g., "Ethan", 42). Literals can only ever be Objects. They sit at the edge of the graph and cannot have outbound relationships.
When a named node (Object) is connected to another named node (Subject) via a named node (Predicate), the graph expands. When it connects to a literal node, the path terminates.

​
Why triples?

Triples follow the RDF (Resource Description Framework) standard. Because every fact shares the same structure, triples compose naturally into a graph—no schema migrations, no table joins. As the graph grows, the agent can traverse relationships to infer new knowledge (for example, that Ethan and Gregory share the same work location).

​
Learn more