Links

Link statements describe how one entity is connected to another. In this pattern, the property names the relationship and the object identifies the related entity. The object is used as another entity in the relationship, not as the value of a property.

• SHOULD use this pattern when the goal of the statement is to relate the subject to another entity as an entity.
• SHOULD NOT author both directions of the same inverse relationship for the same fact.

Link Statement Parts

Subject: The entity the link starts from.

Property: The relationship being described.

Object: The entity linked to the subject.

• MUST be another non-Literal Entity Type.

Examples

Link statements describe relationships between entities.

Person | schema:affiliation | Organization

CreativeWork | schema:creator | Person

Event | schema:location | Place

Links vs Attributes

Use Links when the object is another entity being related as an entity.

Person | schema:affiliation | Organization

Use Attributes when the object functions as the value of a property.

Person | schema:name | "Alice"

Inverse Direction

Some link properties have inverse forms, such as schema:hasPart and schema:isPartOf.

Both directions may be valid at the protocol level, but producers SHOULD choose one canonical authored direction for a given fact and avoid storing both directions redundantly.

For part-whole relationships, FCP strongly encourages schema:hasPart as the canonical authored direction.

Neo4j Labs | schema:hasPart | Neo4j Labs MCP Servers

Consumers MAY interpret or query the inverse relationship when needed without requiring that the inverse statement also be authored.