Graph Schema Reference

A complete specification of the Aevum Encyclopedia knowledge graph. Defines node labels, relationship types, property constraints, and query patterns for building accurate, traversable knowledge structures.

Note: This schema is backward-compatible. New relationship types and properties are additive. Breaking changes are documented in the versioning section and always preceded by a deprecation notice.

Node Types

The knowledge graph is composed of 8 primary node types. Each node represents a distinct semantic entity within the encyclopedia ecosystem.

r>
Label Description Key Properties Cardinality
Concept Core topics, ideas, theories, or phenomena title, description, domain N
Entity Physical objects, places, organizations, people name, type, geo_coordinates N
Source Primary references, publications, datasets doi, publisher, year N
Contributor Authors, editors, domain experts orcid, affiliation, role N
Category Taxonomic grouping nodes path, parent_id N
Event Historical or temporal occurrences start_date, end_date, location_id N
Verification Fact-checking and confidence metadata score, reviewer_id, status 1..1
Translation Multilingual variants of concepts lang_code, localized_title 1..N

Relationship Types

Relationships define semantic connections between nodes. All edges are directed and may carry typed properties.

Type Source → Target Description Properties
REFERENCES Concept → Source Cites or derives from a primary source citation_format, relevance
PART_OF Concept → Category Taxonomic classification confidence, reviewed_by
DEFINED_BY Concept → Concept Forms a definitional or logical dependency relation_type
AUTHORED_BY Source → Contributor Authorship or editorial contribution role, order
OCCURRED_AT Event → Entity Spatial-temporal grounding geo_hash, temporal_range
RELATED_TO Concept ↔ Concept Semantic association or cross-reference weight, context
VERIFIED_BY Concept → Verification Quality assurance linkage method, timestamp

Property Dictionary

Common properties across node types follow strict typing and validation rules. Optional fields are marked with ?.

Validation: All datetime fields must conform to ISO 8601. Numeric confidence scores are floats in [0.0, 1.0]. Text fields are UTF-8 encoded with a 256KB soft limit.