Jeiel the father of Gibeon lived in Gibeon. His wife’s name was Maacah.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
yə·ʿū·ʾēl ’ă·ḇî- ū·ḇə·ḡiḇ·‘ō·wn yā·šə·ḇū ḡiḇ·‘ō·wn ’iš·tōw wə·šêm ma·‘ă·ḵāh
The Fallible · Synthetic · Study Bible
The Descendants of Saul
1 Chronicles 9:35–41 — The Descendants of Saul. Each verse below carries the full apparatus: the Berean Standard Bible, the vocalized original (tap any word), and a parsed breakdown of every term transcribed from the interlinear. Synthesized commentary, canonical threads, and the reading of Christ gather at the end, over the whole unit.
Jeiel the father of Gibeon lived in Gibeon. His wife’s name was Maacah.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
yə·ʿū·ʾēl ’ă·ḇî- ū·ḇə·ḡiḇ·‘ō·wn yā·šə·ḇū ḡiḇ·‘ō·wn ’iš·tōw wə·šêm ma·‘ă·ḵāh
Abdon was his firstborn son, then Zur, Kish, Baal, Ner, Nadab,
Berean Standard Bible · CC0
Hebrew — tap a word ↓
‘aḇ·dō·wn hab·bə·ḵō·wr ū·ḇə·nōw wə·ṣūr wə·qîš ū·ḇa·‘al wə·nêr wə·nā·ḏāḇ
Gedor, Ahio, Zechariah, and Mikloth.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḡə·ḏō·wr wə·’aḥ·yōw ū·zə·ḵar·yāh ū·miq·lō·wṯ
Mikloth was the father of Shimeam. They too lived alongside their relatives in Jerusalem.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·miq·lō·wṯ hō·w·lîḏ ’eṯ- šim·’ām hêm wə·’ap̄- yā·šə·ḇū ne·ḡeḏ ’ă·ḥê·hem ḇî·rū·šā·lim ‘im- ’ă·ḥê·hem
Ner was the father of Kish, Kish was the father of Saul, and Saul was the father of Jonathan, Malchishua, Abinadab, and Esh-baal.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
wə·nêr hō·w·lîḏ ’eṯ- qîš wə·qîš hō·w·lîḏ ’eṯ- šā·’ūl wə·šā·’ūl hō·w·lîḏ ’eṯ- yə·hō·w·nā·ṯān wə·’eṯ- mal·kî- šū·a‘ wə·’eṯ- ’ă·ḇî·nā·ḏāḇ wə·’eṯ- ’eš·bā·‘al
The son of Jonathan: Merib-baal, who was the father of Micah.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇen- yə·hō·w·nā·ṯān mə·rîḇ bā·‘al ū·mə·rî- ḇa·‘al hō·w·lîḏ ’eṯ- mî·ḵāh
The sons of Micah: Pithon, Melech, Tahrea, and Ahaz.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇə·nê mî·ḵāh pî·ṯō·wn wā·me·leḵ wə·ṯaḥ·rê·a‘
The verse-by-verse work is done. What follows gathers the whole unit. All three layers below are machine-generated (⚙). Weigh them; they have no authority.
AI synthesis — woven from the public-domain voices above and the original text; generated and fallible.
Five of this unit's ten commentators say the same thing in different words, and they say it first: this register has been read before. Barnes calls it "An almost exact repetition of 1 Chronicles 8:29-38" and holds it to be "probably intentionally made by the author." Poole names the figure, epanalepsis, "which is frequent both in sacred and profane writers." Cambridge says it is repeated "to serve as an introduction to the story of the death of Saul." K&D agrees and adds the textual judgment that this copy descends from "another document in more complete preservation" than the one in chapter 8. Ellicott, weighing both copies, finds this one "on the whole, in better preservation" with a single loss, Ahaz. ⚙ The Hebrew supports them from underneath: verse 35 sets the clan in Gibeon with the plural perfect יָשְׁבוּ, and verse 38 sets a branch in Jerusalem with the identical form, so the two halves of the section are stitched by one verb. Gill notices the one thing the earlier copy lacks, the founder's name itself, "which is not in 1 Chronicles 8:29." A repetition that adds a name is not a copyist's stutter.
⚙ The register's spine is a single Hiphil: הוֹלִיד (yâlad H3205, "to bear young"), the causative that hands a mother's act to a father. It falls once at verse 38 for Mikloth, three times in verse 39 to run Ner to Kish to Saul to his four sons, and once more in verse 40 for Merib-baal. BSB renders all five as "was the father of", which is accurate and silent: a state where Hebrew has a blow struck five times. Barnes gives the reason the chain exists at all, that the chronicler "re-introduces the genealogy of the person with whose death his historical section opens"; K&D says the register "forms here the introduction to the narrative of Saul's death in 1 Chronicles 10:1-14, which in turn forms the transition to the kingship of David." ⚙ So the verb of generation is pointed at a grave. The fifth stroke is the one that matters for what comes after: after the line has been carried to a crowned king and the king has been carried to Gilboa, the same verb, unchanged, carries one surviving grandson into a list of ordinary men.
⚙ Three times in this short unit the name of a Phoenician deity stands in the ancestry and posterity of Israel's first king: Baal at verse 36 (H1168, which the brief's lexicon glosses without euphemism), Esh-baal at the end of verse 39, Merib-baal and Meri-baal twice over at verse 40. Strong's own entry at H792 carries the later fix in its parenthesis, "Eshbaal (or Ishbosheth)", the substitution of bosheth, shame, for the god's name. Chronicles does not make that substitution. It also does not moralise: four words after Baal in verse 36 stands Zur, which Ellicott reads as "a Divine title" beside Pedahzur and Zurishaddai, and one verse later stands Zechariah with the element yāh in its own letters. The house held both. At the other end, the register that Ellicott judges the better preserved of the two loses exactly one name: "Only the name of Ahaz has fallen out ( 1Chronicles 9:41 )." Geneva's English still prints it; BSB brackets it; the Hebrew words counted in this unit stop at Tahrea. ⚙ A chapter about knowing who belongs, as Henry reads it, ends by showing that the record itself has a hole in it.
⚙ This is the tool's own fallible reading, offered to be tested. Scripture here does almost nothing that we would call writing: it repeats a list, and the repetition is the argument. Poole is right to call it epanalepsis, a resumption made on purpose, and Barnes and K&D are right that it is aimed at chapter 10, where Saul dies. What I want to press is what the aim costs the list. The Chronicler had every reason to clean this register. He could have dropped Baal from the ancestry, replaced Esh-baal with the form that says shame, harmonised the Kish of verse 36 with the Kish of verse 39, and supplied the Ahaz his other copy has. He did none of it. He handed on a house with a foreign god's name in its mouth, an unresolved seam in its middle, and a hole at its end, and then told the story of its death. That is a canon that does not protect itself. And the plainest reading of why such a list was kept is Henry's: it was "to direct the Jews, when they returned out of captivity, with whom to unite, and where to reside." Men coming home from Babylon needed to know whose they were, and God gave them, for that purpose, an honest record rather than a flattering one. ⚙ I take this to be the register's own theology: the God who is "the God of order", in Henry's phrase, keeps order by telling the truth about a failed house, and by keeping, in the last three verses, a line that no longer rules and is still written down.
Not Scripture, a reading offered for testing: the Chronicler copied the house of Saul twice and corrected neither copy, because a record that flatters cannot tell a returning exile who he is.
AI-generated connections. Each carries a verification badge with a recorded basis; contested links are flagged.
This unit is a second copy of the Benjamite and Saulide register in 1 Chronicles 8, and the link is not an impression but a measurable one. The Verifier's candidates return the rare lexemes shared with 8:33, 8:34 and 8:35: מְרִיב בַּעַל (H4807, in 2 verses in the whole canon), פִּיתוֹן (H6377, in 2 verses), and מַלְכִּי־שׁוּעַ (H4444, in 5). Names that occur in only two verses of Scripture, appearing here and there, make the two passages one text. The commentators say so independently and unanimously: Barnes ("An almost exact repetition"), Poole (epanalepsis), Cambridge, Ellicott, Gill and K&D. Ellicott adds the caution that keeps this from being a mechanical copy: "The correspondence of the two lists appears to be too exact to justify an assumption of different original sources", yet K&D argues from the deviations that this copy rests on a better preserved document. Both cannot be pressed at once, and the brief's sources do not settle it.
1 Chronicles 8:33 · 1 Chronicles 8:34 · 1 Chronicles 8:35
basis: Verifier: shared Hebrew lexemes H4807 Mᵉrîyb Baʻal (in 2 vv), H6377 Pîythôwn (in 2 vv), H4444 Malkîyshûwaʻ (in 5 vv), H7027 Qîysh (in 17 vv), H5369 Nêr (in 16 vv), H4318 Mîykâh (in 29 vv). Two of the lexemes occur in only two verses of the canon, so this is a verbal identity of text, not a shared theme; no quotation of one book by another is claimed, since both passages are in Chronicles.
Verse 39 names Saul's sons: Jonathan, Malchishua, Abinadab, Esh-baal. Three of those names recur together in the narrative of Saul's death, which the Verifier confirms at 1 Samuel 31:2 and 1 Chronicles 10:2 through the rare lexeme מַלְכִּי־שׁוּעַ (H4444, in 5 verses in all) together with H3083 Jonathan, H41 Abinadab and H7586 Saul. ⚙ Every occurrence of Malchishua's name in Scripture belongs to the story of this one house and its end, which is what makes the link verbal rather than thematic. The commentators name the same connection from the other direction: Barnes says the chronicler re-introduces the genealogy "of the person with whose death his historical section opens", K&D that it introduces "the narrative of Saul's death in 1 Chronicles 10:1-14", Cambridge that it serves "as an introduction to the story of the death of Saul." The list is a roll call read out just before the battle.
1 Samuel 31:2 · 1 Chronicles 10:2
basis: Verifier: shared Hebrew lexemes H4444 Malkîyshûwaʻ (in 5 vv, rare), H3083 Yᵉhôwnâthân (in 74 vv), H41 ʼĂbîynâdâb (in 11 vv), H7586 Shâʼûwl (in 335 vv). The rare lexeme carries the link; it is a verbal (shared-name) link within Hebrew Scripture, and no citation of one passage by the other is claimed.
Verse 36 lists both Kish and Ner among the sons of Jeiel; verse 39 makes Ner the father of Kish. The unit therefore holds two arrangements of the same two names without reconciling them, and Ellicott, working at verse 36, admits the strain openly: on his conjecture that Baal and Nadab were once the single name Baal-nadab, "In that case Ner is out of place." The Verifier puts the same two lexemes together again at 1 Samuel 14:51 and 1 Chronicles 26:28. ⚙ I note the tension and leave it; none of the ten commentators in this brief resolves it, and I will not manufacture a harmony they declined to offer.
1 Samuel 14:51 · 1 Chronicles 26:28
basis: Verifier: shared Hebrew lexemes H7027 Qîysh (in 17 vv) and H5369 Nêr (in 16 vv) at both references. The lexemes are confirmed; the relation of the two men is what differs between passages, so the link is a shared configuration of names, not a quotation, and no harmonisation is asserted.
Ahio (H283, a rare lexeme, 6 verses) stands at verse 37 and Abinadab (H41, 11 verses) at verse 39. The Verifier finds that same pair of names together at 2 Samuel 6:3, 2 Samuel 6:4 and 1 Chronicles 13:7, which is the ark narrative as I recall it, though this brief carries no text from 2 Samuel and I do not quote it. ⚙ The lexemes are certain; the men are not. The brief's own lexicon says Abinadab is "the name of four Israelites", so a shared name here is not a shared person, and not one of this unit's commentators draws the connection. What can honestly be said is that two uncommon names recur as a pair in a Benjamite setting, and that the reader who follows the link should expect a different household at the other end.
2 Samuel 6:3 · 2 Samuel 6:4 · 1 Chronicles 13:7
basis: Verifier: shared Hebrew lexemes H283 ʼAchyôw (in 6 vv) and H41 ʼĂbîynâdâb (in 11 vv) at all three references. The pairing of two uncommon names is the recorded pattern; no identification of the persons is claimed, and the lexicon itself records four bearers of Abinadab.
Mikloth (H4732) is one of the rarest lexemes in the unit: four verses in the whole canon by the Verifier's count, two of them here (verses 37 and 38). The Verifier's strongest non-Chronicles-8 candidate is 1 Chronicles 27:4, where the name appears twice in David's military rota. ⚙ The lexeme link is exact. The identification is not: a Benjamite of Gibeon in a register of Saul's kindred and an officer in David's standing divisions may or may not be one man, and no commentator in this brief addresses it at all. I record the link and flag it rather than build on it.
1 Chronicles 27:4
basis: Verifier: shared Hebrew lexeme H4732 Miqlôwth (in 4 vv, rare), counted twice at the reference. The lexeme is confirmed, but the claim a reader would want (that the same man is meant) is unsupported by any source in this brief and is contested in the wider literature. Verify before use.
⚙ The one place the New Testament is commonly said to reach back into this exact genealogy is Paul's survey of Israel's history at Pisidian Antioch, where Saul is identified as the son of Kish, of the tribe of Benjamin. If that is what Acts 13:21 says, then the apostolic preaching used the same two names this verse 39 joins, and used them for the same purpose Barnes and K&D assign to the Chronicler: to get from a king who failed to David. I flag the link rather than assert it. It is not in the Verifier's candidate list, it cannot rest on shared Strong's numbers because the one text is Greek and the other Hebrew, and I am citing Acts from memory rather than from this brief, which contains no New Testament text at all.
Acts 13:21 · 1 Chronicles 9:39
basis: Not in the Verifier's candidate list and not verifiable by shared lexemes: the link is cross-Testament (Greek to Hebrew), so no verbal tier is possible in principle. The basis is the claim that Acts 13:21 names Saul son of Kish of Benjamin, which this brief does not source. Check the text before relying on it.
AI-generated reading; weigh it against the text.
The sources of this unit agree, with unusual unanimity, on why these seven verses exist. Barnes: the chronicler "re-introduces the genealogy of the person with whose death his historical section opens." K&D: the register "forms here the introduction to the narrative of Saul's death in 1 Chronicles 10:1-14, which in turn forms the transition to the kingship of David." Cambridge: an introduction "to the story of the death of Saul." Ellicott: "the account of that king's final ruin in 1 Chronicles 10." Gill: it is made "to lead on to and connect the following history of the kings of Judah." ⚙ Read redemptive-historically, that is the shape of the whole Old Testament in miniature: a house is named in full, honoured with its firstborn and its cities, and then set down so that the house of David may be taken up, and the line of Judah runs from there to the one whom the New Testament calls David's son. The reading is not novel; it is the settled judgment of every commentator in this brief, though each of them states it as literary purpose and the christological extension is mine.
1 Chronicles 10:2 · 1 Chronicles 9:39
JFB, commenting a few verses earlier in this same chapter on the king's gate, records what the post exilic community did with a door no king used: "although there was no king in Israel on the return from the captivity, yet the old ceremonial was kept up, probably in the hope that the scepter would, ere long, be restored to the house of David." ⚙ That is the disposition in which a returned exile would copy out a dead king's family tree. The gate is kept because a king is expected; the genealogies are kept for the same reason, and Henry says the chapter's purpose was to tell the returning people "with whom to unite, and where to reside." Christians have read that expectation as answered in the one born of David's line. Two honesty notes: JFB's sentence belongs to 1 Chronicles 9:18, not to these verses, and the hope he describes is his historical reconstruction of the returnees' motive, not a statement of the text.
1 Chronicles 9:18 · 1 Chronicles 9:35
⚙ This reading is mine and I mark it novel. Saul's house carries Baal's name three times in seven verses: Baal in verse 36, Esh-baal in verse 39, Merib-baal and Meri-baal in verse 40. The brief's own lexicon at H792 preserves the later correction in a parenthesis, "Eshbaal (or Ishbosheth)", where bosheth, shame, is put in the god's place: Israel's memory of its first royal family had to have a word for shame written into it. Chronicles declines to make the substitution and hands the names on unretouched. ⚙ Set against that, the canon's answer to a house whose names required covering is a king whose name required no covering and who was given a name to be confessed rather than repaired. I claim no verbal link here and none exists: the observation is the contrast between a genealogy that had to be edited for shame and a gospel that hangs on a name that never was. Tested against the text of this unit, the most that can be said is that Chronicles refused the edit.
1 Chronicles 9:39 · 1 Chronicles 9:40
The biblical text is the Berean Standard Bible (BSB), public domain (CC0). Hebrew/Greek text, transliteration, morphology and Strong’s are transcribed from the Berean interlinear (CC0) + Strong’s lexicons (PD); the literal renderings, divergence notes, word notes and all synthesis are this tool’s own work (⚙) — fallible; verify them.
Named voices, quoted verbatim from public-domain works:
Text. The Hebrew of this unit ends at Tahrea in verse 41; BSB prints "[and Ahaz]" in brackets because the name stands in the parallel register and in the received English tradition (Geneva: "and Tahrea, and Ahaz") but not among the words counted here. Ellicott states the loss directly. Verse 38's last word is written in the source with a final samekh after the verse mark, the Masoretic sign of a section break; the royal line proper begins at verse 39.
The interlinear as captured. Three defects in the source data are visible and are recorded rather than repaired. (1) Verse 35 has its gloss column offset: the word parsed as conjunctive waw plus preposition beth is glossed "of Gibeon" and the bare proper noun is glossed "in Gibeon", which is the reverse of the parse. (2) In verse 39 the parse column is displaced across indices 13 to 16, where object markers are parsed as proper nouns and proper nouns as object markers, because the compound name Malchi-shua occupies two rows. (3) The gloss "vvv" at 9:39 index 13 and 9:40 indices 2 and 4 is the source's placeholder for the first element of a hyphenated name, not a Hebrew word.
Lexicon. The brief's entries for H4807 and H4810 both gloss the name as "an epithet of Gideon", which cannot be correct for Jonathan's son; the discrepancy is flagged and left unresolved, since correcting a source is not within this layer's authority. H2148, H7586 and H4429 are given in the brief as identifications only, with no etymology, so every etymological remark on Zechariah, Saul and Melech in these notes is marked as my own reading.
Sources. Ten commentators are attached to this passage, but their coverage is thin and uneven, and the reader should know it. Gill's note is the same paragraph on 9:35 repeated at every verse of the unit; so are Henry's (a single note on the whole chapter), Barnes's and K&D's. JFB's block here is his comment on 1 Chronicles 9:18, the king's gate, and says nothing about these verses; it is cited once, with that stated. Poole has text only at 9:35 and explicitly none at 9:36 through 9:41. Cambridge appears at 9:35 and 9:39, and its 9:35 entry is damaged ("repeated here in ler" for "in order"). Pulpit's entire entry for this unit is the cross reference "Verses 35-44. - (See last chapter, vers. 29-40.)", which is why no Pulpit voice appears. Geneva's entries at these verses are the verse text itself rather than marginal glosses, and are cited twice only as textual witnesses (Eshbaal at 9:39, Ahaz at 9:41), with that noted in place.
What is uncertain. Whether Kish and Ner stand in one relation or two (verse 36 against verse 39 and 1 Samuel 14:51); whether the Mikloth of verses 37 and 38 is the Mikloth of 1 Chronicles 27:4; whether the two copies of this register descend from one document or two, on which Ellicott and K&D pull in opposite directions. The Acts 13:21 thread is flagged because it is cited from memory and this brief carries no New Testament text.
✦ = human, public-domain source, quoted and named. ⚙ = machine synthesis, to be verified. Flagged cross-references are left visible on purpose — the verifier working in the open. “Search the Scriptures daily, whether those things were so.” (Acts 17:11)