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)'}

4 rows where subject_entity_id = "ENT_HTT_KUMARBI"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: source_id

relationship_id ▼ subject_entity_id relationship_type object_entity_id confidence rationale source_id review_status period_id
1478 Kumarbi ENT_HTT_KUMARBI received_as Kronos ENT_KRONOS high The Kumarbi→Kronos parallel is the centerpiece of West's (1997) argument for Near Eastern influence on Hesiod's Theogony. Both deities share an exact structural role: (1) they overthrow the ruling sky deity by biting/castrating the genitals (Kumarbi bites off Anu's genitals; Kronos castrates Ouranos with a sickle); (2) they absorb divine seed and become pregnant with the deity who will overthrow them; (3) they are themselves defeated by the storm deity son (Teshub/Zeus). This three-stage narrative is unique to the Kumarbi cycle among Near Eastern texts and uniquely explains why Hesiod's Theogony has the same three-stage structure. Transmission most likely via Anatolian-Greek contact in the 8th-7th c. BCE. Martin L. West, The East Face of Helicon: West Asiatic Elements in Greek Poetry and Myth (Oxford: Clarendon Press, 1997) SRC_WEST_EAST_HELICON reviewed Archaic Period PER_GRK_ARCHAIC
5962 Kumarbi ENT_HTT_KUMARBI member_of The Hittite Pantheon ENT_HTT_PANTHEON high Kumarbi is the former king of the gods in the Hurrian-Hittite theogony. Walter Burkert, The Orientalizing Revolution: Near Eastern Influence on Greek Culture in the Early Archaic Age (Harvard University Press, 1992) SRC_BURKERT_ORIENT_REV reviewed  
5980 Kumarbi ENT_HTT_KUMARBI parent_of Ullikummi ENT_HTT_ULLIKUMMI high Kumarbi fathers the stone monster Ullikummi (Song of Ullikummi) to overthrow Teshub. Walter Burkert, The Orientalizing Revolution: Near Eastern Influence on Greek Culture in the Early Archaic Age (Harvard University Press, 1992) SRC_BURKERT_ORIENT_REV reviewed  
5981 Kumarbi ENT_HTT_KUMARBI opposes Teshub ENT_HTT_TESHUB high The Kumarbi cycle's central conflict is Kumarbi's attempts to depose his son Teshub. Walter Burkert, The Orientalizing Revolution: Near Eastern Influence on Greek Culture in the Early Archaic Age (Harvard University Press, 1992) SRC_BURKERT_ORIENT_REV reviewed  

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]);