✦ DeityDB
Browse Graph Connections Timeline Lineages Path Map Queries About Collaborate API GitHub ↗

entity_relationships: 1480

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

This data as json

relationship_id subject_entity_id relationship_type object_entity_id confidence rationale source_id review_status period_id
1480 ENT_HTT_TESHUB aligned_with ENT_ZEUS low [RETYPED v2.1.60 received_as->aligned_with, high->low: West (East Face of Helicon) argues literary transmission of the succession/storm-champion NARRATIVE pattern, not that the god Zeus derives from Teshub; Zeus's name is an independent IE inheritance (*Dyeus). Typological/motif alignment only. The Ullikummi->Typhon motif chain (edges 1482/1483) remains as reception.] Teshub and Zeus share the role of the storm deity champion who defeats a monstrous adversary (Ullikummi/Typhon) and the usurper predecessor (Kumarbi/Kronos) to establish the current divine order. West (1997) documents that the narrative structure of Zeus's ascent in Hesiod's Theogony follows the Kumarbi cycle more closely than any other Near Eastern text. Both Teshub and Zeus also create an ordered cosmos out of the pre-existing chaos. The transmission pathway runs through Anatolian-Ionian Greek contact in the Archaic period. SRC_WEST_EAST_HELICON needs_review PER_GRK_ARCHAIC
Powered by Datasette · Queries took 319.494ms · Data license: MIT · Data source: jebboone/deitydb