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

3 rows where subject_entity_id = "ENT_ELAM_NAPIRISHA"

✎ 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
2393 Napirisha ENT_ELAM_NAPIRISHA patron_of Healing ENT_HEALING medium Napirisha's association with life-giving water and the Anshan highland springs situates him in the healing and renewal domain. His temples were associated with sacred water sources; his iconography includes the life-water motif; and his name ("the Great God") encompasses the generative divine power from which healing flows. Confidence medium: the healing attribution is inferential from the water-and-life domain rather than directly inscribed in the surviving texts, though the functional parallel with water-healing deities (cf. Enki/Ea) is strong. Potts (1999) p. 244. 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
2394 Napirisha ENT_ELAM_NAPIRISHA aligned_with Enki/Ea ENT_MES_ENKI_EA medium Napirisha and Enki/Ea share the domain of life-giving water as a divine principle — both are associated with the fresh water that sustains life (the Mesopotamian apsû / Napirisha's highland springs), both embody divine wisdom manifest through the water medium, and both serve as the principal "great god" of their respective traditions alongside the supreme sky deity. The geographical proximity of Elam and Mesopotamia and the documented Elamite borrowing of Akkadian scribal culture means these deities' parallel functions would have been apparent to ancient practitioners. Confidence medium: the alignment is structural and domain-based; no ancient source explicitly equates them. Carter & Stolper (1984) p. 50. Elizabeth Carter and Matthew W. Stolper, Elam: Surveys of Political History and Archaeology (University of California Publications, Near Eastern Studies 25; University of California Press, Berkeley / Los Angeles / London, 1984) SRC_CARTER_STOLPER_ELAM reviewed Kingdom of Elam PER_ELAM_CLASSICAL
4133 Napirisha ENT_ELAM_NAPIRISHA parent_of Hutran ENT_ELAM_HUTRAN medium Napirisha is the father of Hutran in the divine triad of Anshan. Elizabeth Carter and Matthew W. Stolper, Elam: Surveys of Political History and Archaeology (University of California Publications, Near Eastern Studies 25; University of California Press, Berkeley / Los Angeles / London, 1984) SRC_CARTER_STOLPER_ELAM 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]);