How to Read a Greek Mythology Family Tree

What does a line on a Greek mythology family tree actually mean?

Its meaning depends on the chart’s legend and evidence. Parentage, primordial emergence, partnership, and a hostile encounter are different relationships; a figure’s vertical position also need not establish a universal chronology.

Read the kind of line before following it

MythBranch distinguishes parent, emergence, union, and encounter connections. A parent line from Zeus to Perseus makes a genealogical claim. An encounter line from Perseus to Medusa records their meeting in a story. Following both lines as though they belonged to a single descent chain would incorrectly make Medusa a descendant of her killer. The legend is therefore part of the argument, not decoration.

Partnership also needs care. A connection can identify a relationship associated with a child without certifying a marriage, a lasting household, or consent. Ancient accounts describe relationships under widely different conditions. The profile and source passage must supply those conditions. A small chart cannot safely make every union look like the same domestic institution.

Emergence does not require an ordinary pair of parents

At Theogony 116–132, Chaos appears first in Hesiod’s sequence, followed by Gaia, Tartarus, and Eros. Erebus and Night arise from Chaos; Gaia bears Uranus and Pontus without an ordinary two-parent structure. A modern reader may want every node attached to a couple, but supplying a second parent would change the account. Empty space can preserve a meaningful feature of the source.

The distinction is especially important when a name also denotes a place or condition. Gaia is Earth, Uranus is Sky, and Tartarus is both a named primordial power and a cosmic region. Their genealogical relationships help describe the formation of a world. Treating all these births as episodes in an ordinary household loses the physical and cosmic meanings carried by the names.

Vertical position is an editorial arrangement

A diagram needs rows, spacing, and a direction in which lines can travel. MythBranch uses those arrangements to keep selected relationships readable. They should not be interpreted as a dated timeline or a definitive sequence for the birth of every figure. Figures grouped as heroes or monsters can have very different ancestral distances from a particular god.

The surviving texts supply a direct warning. Hesiod calls Zeus the youngest child of Rhea; Zeus claims seniority over Poseidon in Iliad 15. A chart can draw the shared parents consistently while leaving the disputed age order to prose. This is a case in which adding more apparent precision to the picture would make the evidence less accurately represented.

Omission and disagreement require different notes

Athena’s short branch can show Zeus while the profile discusses Metis and the swallowed pregnancy in Theogony 886–900. The missing visible mother is a consequence of chart scope. Aphrodite presents a different problem: Hesiod’s sea birth and the Iliad’s Zeus-and-Dione genealogy offer alternatives. One omitted relationship and two competing accounts should not receive the same explanation.

Likewise, the atlas’s seven individually represented Titans do not replace Hesiod’s list of twelve. A selected graph is not a census. Check the era directory for the wider group, then consult the figure profile for omitted parents, descendants, or disputed relationships. Counting visible nodes answers a question about this diagram; it does not automatically answer a question about ancient tradition.

Test a path with a concrete reading

Start with Gaia, move through Uranus and Cronus, and then follow Zeus to Athena. At each step, ask what the edge means and what evidence supports it. Gaia’s production of Uranus differs from her later union with him; Cronus’s overthrow of Uranus is an event added to their parent-child relation; Athena’s emergence from Zeus has a story involving Metis that a short line cannot show.

Next open Perseus and compare his parental connection with his encounter with Medusa. Library 2.4.1–3 gives narrative circumstances surrounding both relationships. This small exercise demonstrates a useful reading discipline: keep ancestry separate from action, recover the source, and return to the chart only after the distinction is clear. The sibling guide then provides a focused comparison of shared parents, half-siblings, and conflicting birth order.

Test the comparison in individual lives

Each profile brings the question back to a particular figure, an ancient passage, and the limits of the diagram.

Questions this comparison raises

Sources and editions

1. Hesiod, Theogony ↗

   H. G. Evelyn-White, 1914 public-domain translation. Passage ranges are specified in each discussion.

2. Homer, Iliad 15.158–217 ↗

   A. T. Murray, 1924 public-domain translation. Zeus’s command and Poseidon’s response preserve rival claims to authority.

3. Homer, Iliad 5.370–430 ↗

   A. T. Murray, 1924 public-domain translation. Aphrodite’s parents in this account.

4. Pseudo-Apollodorus, Library 2.4.1–3 ↗

   J. G. Frazer, 1921 public-domain translation. Perseus’s birth and expedition against the Gorgons.

Passage references identify the ancient evidence; the interpretive argument is MythBranch's reading. Cite the edition you consult and preserve disagreements between sources.