Verse Lens · Expanded explanation
Genesis 36:15 Explained in Context
Use this verse as a doorway into the larger passage—not as an isolated saying.
Verse 15. 15These were dukes of the sons of Esau: the sons of Eliphaz the firstborn son of Esau; duke Teman, duke Omar, duke Zepho, duke Kenaz,
King James Version — public domain in the United States · Bible text and permissions
Quick Meaning
The list now identifies chiefs from Esau's lines, beginning with Eliphaz's descendants. The KJV's 'duke' means a chief or clan leader, not a medieval European noble.
Read It With
- Genesis 36:9–30
Read verses 15–19 with verses 10–14. The first list gives descendant relationships; the second reuses many names as chiefs, showing how family memory and clan leadership are connected.
Why This Verse Appears Here
After the descendants are named, the text restates their lines as chiefs to show clan leadership within Edom.
Read Genesis 36:15–19 together
Why these verses belong together: The descendant branches are recast as chiefs under the three maternal lines and summarized under Esau-Edom.
Verse 15. 15 These were dukes of the sons of Esau: the sons of Eliphaz the firstborn son of Esau; duke Teman, duke Omar, duke Zepho, duke Kenaz,
Verse 16. 16 Duke Korah, duke Gatam, and duke Amalek: these are the dukes that came of Eliphaz in the land of Edom; these were the sons of Adah.
Verse 17. 17 And these are the sons of Reuel Esau’s son; duke Nahath, duke Zerah, duke Shammah, duke Mizzah: these are the dukes that came of Reuel in the land of Edom; these are the sons of Bashemath Esau’s wife.
Verse 18. 18 And these are the sons of Aholibamah Esau’s wife; duke Jeush, duke Jaalam, duke Korah: these were the dukes that came of Aholibamah the daughter of Anah, Esau’s wife.
Verse 19. 19 These are the sons of Esau, who is Edom, and these are their dukes.
Follow the Context
- The renewed toledot identifies Esau as father or ancestor of Edom in Seir (36:9).
- Esau's descendants are traced through Adah-Eliphaz, Bashemath-Reuel, and Aholibamah, with Timna and Amalek noted within Eliphaz's line (36:10–14).
- The descendant names are organized again as chiefs from Eliphaz, Reuel, and Aholibamah in Edom (36:15–19).
- Seir's Horite descendants are listed, including Lotan's sister Timna and Anah's discovery while tending Zibeon's donkeys (36:20–28).
- Seven Horite names are repeated as chiefs according to their clans in Seir (36:29–30).
Phrase-by-Phrase Explanation
“dukes”
In plain language: Chiefs or leaders associated with clans.
The descendant names are now presented in Edom's leadership structure.
Why it matters: The KJV term can mislead readers into importing a European rank.
How certain? very strong“sons of Eliphaz”
In plain language: Leaders are grouped under Eliphaz's family branch.
Genealogical descent and clan organization overlap in the list.
Why it matters: The wording may compress individuals, founders, and clan identities.
How certain? strong“firstborn son of Esau”
In plain language: Eliphaz is identified by birth position within Esau's named sons.
The label orders the genealogy before other maternal branches.
Why it matters: Birth order structures the list but is not moral approval or a universal leadership rule.
How certain? very strongWhat This Verse Is Not Saying
The KJV word 'duke' does not refer to medieval European nobility.
This chief list does not establish exact dates, borders, population totals, succession rules, or one permanent constitutional system.
Calling Eliphaz Esau's firstborn does not make every later chief morally superior or spiritually chosen.
The list does not rank clans or modern peoples by human worth.
What Remains True
Leadership titles should be interpreted within their own social world, and a repeated family name may represent a clan as well as an individual leader.
How It Can Shape Life
- Before applying an ancient title to modern government or church office, explain its actual context and avoid building a complete institution from a short list.
Teach It Back
Explain Genesis 36:15's contribution to Genesis 36:9–30. Include why the nearby verses are required, what the verse clearly says, and one conclusion it does not justify.
Your explanation stays in this browser. It is not sent or saved.
Continue in Context
The full thought-unit study remains the final contextual authority for this Verse Lens.
Read Genesis 36:9–30 — Esau's Descendants and Seir's Clans Are RecordedSources used for this Verse Lens
How certain is this explanation? strong
Where care is needed
The exact office, scale, duration, and territorial scope of an alluf are not fully defined by Genesis 36.
Some names may designate an individual, clan, place, or several related memories.
These are the sources used directly for this lens. Language, grammar, disagreements, and the complete source shelf remain attached to the full thought-unit research record.
Biblical text
King James (Authorized) Version — eng-kjv2006
eBible.org and CrossWire Bible Society
USFM archive eng-kjv2006_usfm.zip; source files dated 2026-08-19; downloaded 2026-08-24; archive SHA-256 aec1b3b26c622fd3d963d2bbac963016b9513246ffbfa20da00bb100372ea007; normalized corpus SHA-256 09aef51d90488aa7b9722b3fd9a93f4b25f6bf2064c5fd798fb39673c300ddf2.
Supports: Displayed wording, list sequence, maternal lines, Timna and Amalek, chiefs, Seir and Horite records, Anah's discovery, canonical name comparisons, brotherhood restraint, and later-conflict boundaries.
Exact location: Genesis 36:9–30 in the pinned eng-kjv2006 source; compared with Genesis 15:19; 25:30; 26:34–35; 28:9; 36:1–8, 31–43; 37:1–2; Exodus 17; Deuteronomy 2:4–5, 12, 22; 23:7; 25:17–19; 1 Samuel 15; 1 Chronicles 1:35–42; Job 2:11
Open source ↗hebrew text morphology and lemma data
Open Scriptures Hebrew Bible — Genesis
Open Scriptures Hebrew Bible Project
Open Scriptures, Version 2.2 released 2021; repository inspected 2026
Supports: Hebrew genealogical, social-status, political, people-group, gender-inclusive, and obscure-word evidence.
Exact location: Open Scriptures Hebrew Bible, wlc/Gen.xml, Genesis 36:9–30; forms and syntax for toledot, father, sons or descendants, concubine, alluf chiefs, Horite, inhabitants, sister, yēmim, children including a daughter, and chief lists
Open source ↗Translation and textual notes
NET Bible — Genesis with translators' notes
Biblical Studies Press
Biblical Studies Press, Digital edition accessed 2026
Supports: Translation alternatives, KJV-language clarification, material textual variants, Horite restraint, and the uncertainty of Anah's discovery.
Exact location: NET Bible, Genesis 36 and translator notes 7–22 on genealogical father, descendants, chiefs, Korah, Seir and Horites, Hemam, Shepho, yēmim, children, and Dishon-Dishan
Open NET Genesis 36 ↗peer reviewed open anthropological historical and genealogical study
‘You Shall Not Abhor an Edomite, for He Is Your Brother’: The Tradition of Esau and the Edomite Genealogies from an Anthropological Perspective
Juan Manuel Tebes
The Journal of Hebrew Scriptures 6, Article 6, 2006 volume; published online 2009
Supports: Edomite and Seirite list structure, possible clan-place functions, social-network complexity, historical-geographical proposals, Amalek placement, and explicit limits of reconstructing ethnicity and history from shared names.
Exact location: Journal of Hebrew Scriptures 6, Article 6, pp. 6–7 on Genesis 36's seven interrelated lists; pp. 14–16 on Esau and Seir names, Judahite and Simeonite parallels, Kenizzites, and Amalek; pp. 20–30 on kinship, segmentation, orality, and the Late Iron Age Negev proposal
Open source ↗