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

2 rows where subject_entity_id = "ENT_ELAM_INSHUSHINAK"

✎ 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
2387 Inshushinak ENT_ELAM_INSHUSHINAK patron_of Dead ENT_DEAD high Inshushinak is explicitly "lord of the dead" in Elamite sources — his judicial function encompasses the fate of souls after death, a role consistent with his position as the supreme city deity of Susa (a major funerary cult center) and with the underworld associations of ancient Near Eastern city gods who control the boundary between living and dead. The "Sit-shamshi" bronze ritual scene from Susa (depicting funerary rites) is associated with his cult. Potts (1999) p. 273. Daniel T. Potts, The Archaeology of Elam: Formation and Transformation of an Ancient Iranian State (Cambridge World Archaeology; Cambridge University Press, Cambridge, 1999) SRC_POTTS_ELAM reviewed Kingdom of Elam PER_ELAM_CLASSICAL
2388 Inshushinak ENT_ELAM_INSHUSHINAK aligned_with Utu/Shamash ENT_MES_UTU_SHAMASH medium Inshushinak and Utu/Shamash are structurally parallel as judicial deities who oversee divine justice and adjudicate the fates of the dead. Both operate at the threshold between life and death as the divine judge of last resort; both are associated with light and truth as the foundations of judgment. The parallel was recognized in antiquity through the close cultural contact between Susa and Mesopotamia: Elamite scribes used Akkadian cuneiform and were well aware of Shamash's judicial role. Confidence medium: no ancient source explicitly equates them, but the structural and functional alignment is strong and frequently noted in modern scholarship. Potts (1999) p. 276. Daniel T. Potts, The Archaeology of Elam: Formation and Transformation of an Ancient Iranian State (Cambridge World Archaeology; Cambridge University Press, Cambridge, 1999) SRC_POTTS_ELAM reviewed Kingdom of Elam PER_ELAM_CLASSICAL

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