Relationships

2,079 typed, source-backed relationships between entities. Each row records a directed relationship (subject → type → object) with a justifying source and rationale note. See relationship_types for the full controlled vocabulary of 70 relationship types. Key types: reception_of / received_as (transmission across traditions), equated_with (interpretatio graeca / analogues), parent_of (genealogy), member_of (collective membership), emanates_from (Gnostic/Neoplatonic structure).

Data license: MIT · Data source: jebboone/deitydb

subject_entity_id
{'description': 'The entity initiating or holding the relationship'}
relationship_type
{'description': 'Typed relationship from the controlled vocabulary (see relationship_types table)'}
object_entity_id
{'description': 'The entity receiving or targeted by the relationship'}
confidence
{'description': 'high / medium / low / speculative'}
rationale
{'description': 'Scholarly justification for the relationship, with source citations'}
source_id
{'description': 'Primary source justifying this relationship'}
period_id
{'description': 'Historical period in which this relationship is attested (null = all periods)'}

1 row where subject_entity_id = "ENT_MES_NAMMU"

✎ View and edit SQL

This data as json, CSV (advanced)

relationship_id ▼ subject_entity_id relationship_type object_entity_id confidence rationale source_id review_status period_id
1595 Nammu ENT_MES_NAMMU parent_of Enki/Ea ENT_MES_ENKI_EA high In Enki and Ninmah (ETCSL 1.1.2), Nammu is explicitly described as Enki's mother: she wakes Enki to help solve the problem of the gods having to do their own labor, and calls him "my son." The Eridu cosmogonic tradition places Nammu as the primordial sea from which Enki/the Abzu emerges; this makes Nammu the generative source of Enki's fresh-water wisdom domain. Electronic Text Corpus of Sumerian Literature SRC_ETCSL reviewed Early Mesopotamian PER_MES_EARLY

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE "entity_relationships" (
   [relationship_id] INTEGER PRIMARY KEY,
   [subject_entity_id] TEXT REFERENCES [entities]([entity_id]),
   [relationship_type] TEXT REFERENCES [relationship_types]([relationship_type]),
   [object_entity_id] TEXT REFERENCES [entities]([entity_id]),
   [confidence] TEXT,
   [rationale] TEXT,
   [source_id] TEXT REFERENCES [sources]([source_id]),
   [review_status] TEXT,
   [period_id] TEXT REFERENCES [periods]([period_id])
);
CREATE INDEX [idx_entity_relationships_period_id]
    ON [entity_relationships] ([period_id]);
CREATE INDEX [idx_entity_relationships_source_id]
    ON [entity_relationships] ([source_id]);
CREATE INDEX [idx_entity_relationships_object_entity_id]
    ON [entity_relationships] ([object_entity_id]);
CREATE INDEX [idx_entity_relationships_relationship_type]
    ON [entity_relationships] ([relationship_type]);
CREATE INDEX [idx_entity_relationships_subject_entity_id]
    ON [entity_relationships] ([subject_entity_id]);