The Fallible Study Bible

The Fallible · Synthetic · Study Bible

1 Chronicles1:18

Public-domain source — quoted & attributed AI synthesis — generated, verify

1 Chronicles 1:18 — . 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.

18

Arphaxad was the father of Shelah, and Shelah was the father of Eber.

Berean Standard Bible · CC0

Hebrew — tap a word ↓

wə·’ar·paḵ·šaḏ yā·laḏ ’eṯ- šā·laḥ wə·še·laḥ yā·laḏ ’eṯ- ‘ê·ḇer

Word by word8 · parsed
וְאַרְפַּכְשַׁ֖דwə·’ar·paḵ·šaḏArphaxadH775
√ ʼArpakshad — Arpakshad, a son of NoahConjunctive wawNounpropermasculine singular
ʼArpakshad: Arphaxad, a son of Noah The conjunctive waw resumes rather than starts: Arphaxad was already listed in verse 17 as a son of Shem, and this verse picks him up again to carry him forward. H775 occurs in only nine verses in all of Scripture, and every one of them sits in a genealogy of Shem (Genesis 10 and 11, here, and 1 Chronicles 1:17 and 1:24). The name exists in the canon for one purpose: to be a link.
יָלַ֣דyā·laḏwas the father ofH3205
√ yâlad — to bear youngVerbQalPerfectthird person masculine singular
yâlad: to bear young (Qal perfect 3ms) A completed act, not an office. This is the verb by which the whole covenant line advances, and in this chapter it marks a structural turn: K&D notes that the register is joined by ûḇenê through verse 9, then by yālaḏ from verse 10, as at Genesis 10:8, and again at verse 18 as at Genesis 10:24. Where yālaḏ takes over, the table of nations has become a pedigree. The same verb governs the entire chain that Matthew will later resume with its Greek counterpart.
אֶת־’eṯ-H853
√ ʼêth — properly, self (but generally used to point out more definitely the object of a verb or preposition, even or namely)Direct object marker
ʼêth: direct object marker Untranslatable particle; it carries no meaning of its own, only pointing to Shelah as the definite object of the begetting.
שָׁ֑לַחšā·laḥShelahH7974
√ Shelach — Shelach, a postdiluvian patriarchNounpropermasculine singular
Shelach: Shelach, a postdiluvian patriarch H7974 is genuinely rare, appearing in only seven verses canon wide. Here it is where the textual question of this verse lands: JFB states flatly that Cainan, the father's name, is omitted here, citing Luke 3:36; Poole allows that Arphaxad begat Shelah either immediately or mediately through Cainan. The Hebrew as it stands names two generations and no more, and the honest reading of the Masoretic line is that it is compressed, not that it is contradicted.
וְשֶׁ֖לַחwə·še·laḥand ShelahH7974
√ Shelach — Shelach, a postdiluvian patriarchConjunctive wawNounpropermasculine singular
Shelach: Shelach, a postdiluvian patriarch The waw plus name repeats the subject so the second clause can stand alone: Shelah is object in the first half of the verse and subject in the second, the pivot on which the chain turns.
יָלַ֥דyā·laḏwas the father ofH3205
√ yâlad — to bear youngVerbQalPerfectthird person masculine singular
yâlad: to bear young (Qal perfect 3ms) The verb repeats without variation, which is the point: the formula is deliberately flat so that the names, not the storytelling, carry the freight.
אֶת־’eṯ-H853
√ ʼêth — properly, self (but generally used to point out more definitely the object of a verb or preposition, even or namely)Direct object marker
עֵֽבֶר׃‘ê·ḇerEberH5677
√ ʻÊbêr — Eber, the name of two patriarchs and four IsraelitesNounpropermasculine singular
ʻÊbêr: Eber, the name of two patriarchs and four Israelites The weightiest word in the verse. Geneva glosses it as the source of the Hebrews, who were later called Israelites of Israel, who was Jacob, and Jews of Judah because of the excellency of that tribe. Cambridge reads the noun rather than the person, since the Hebrew usually means "the land beyond," and proposes a personification of the population beyond the Euphrates. Gill supplies the reason this whole register exists: from Shem, in the line of Heber, sprang Abraham, the ancestor of the Jewish nation. H5677 appears in fifteen verses; from this name the covenant narrows to one man, one land and one promise.

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.

Grand Commentary — the unit, read whole

synthesis · verify

AI synthesis — woven from the public-domain voices above and the original text; generated and fallible.

i. Two begettings, and the narrowing of the world — 1 Chronicles 1:18

The verse contains eight words and two clauses, and both clauses are the same clause: יָלַ֣ד (yā·laḏ, H3205, Qal perfect), a completed begetting, with אֶת־ marking a definite person as its object. Nothing happens here except that a list moves forward by two names. K&D reads that flatness as deliberate architecture: the Chronicler has taken the register from Genesis 10 and stripped out the introductory and concluding remarks, Nimrod's kingdom in Babel, and the settlement notices, leaving bare names, and he notes that where Genesis 10:2-7 joins the sections with ûḇenê the Chronicler does the same in verses 5 to 9, and where Genesis 10:24 uses yālaḏ our verse uses yālaḏ. The change of connector at verse 10 and again here is the change from a table of nations to a line of descent. Gill states the purpose plainly: the posterity of Shem are placed last because from him, in the line of Heber, sprang Abraham, the ancestor of the Jewish nation, of whom the Messiah was to come, and it is for that sake the genealogy is given. ⚙ Our own reading: the seventy-one names of this chapter are a funnel, and verse 18 is the narrowest point yet reached.

ii. The missing generation: JFB, Poole and the honest gap — 1 Chronicles 1:18

Both commentators who address this verse directly address the same problem, and they do not agree on how firmly to hold it. JFB says Cainan, the father's name, is omitted here, and points to Luke 3:36. Poole says Arphaxad begat Shelah either immediately, or mediately by his son Cainan, who is expressed at Luke 3:35, and defers his argument to another place. The difference is not trivial: JFB treats the Hebrew as defective, Poole treats it as compressed. ⚙ Our judgment is that Poole's caution is the better discipline here. Hebrew genealogies demonstrably telescope, yālaḏ does not require immediacy of descent, and the extra Cainan is present in the Septuagint tradition of Genesis 11 and in Luke but absent from the Masoretic text of both Genesis 10:24 and this verse. We record the divergence and do not resolve it. Notice too that JFB and Poole cite adjacent but different verses in Luke's chain, which is itself a small warning about how tightly cross references should be held.

iii. Eber, or the land beyond — 1 Chronicles 1:18

The last word of the verse is the one the chapter has been travelling toward. Geneva takes עֵֽבֶר׃ (‘ê·ḇer, H5677) as a person and a fountainhead: of him came the Hebrews who were later called Israelites of Israel, who was Jacob, and Jews of Judah because of the excellency of that tribe. Cambridge takes the same consonants as a noun, observing that the Hebrew word usually means "the land beyond," and proposing that what we have here may be a personification of the population beyond the Euphrates. K&D pushes back on that whole approach, arguing against Bertheau that Arphaxad, Shelah, Eber, Peleg and Joktan are names of persons, the tribal ancestors, and that reading them as peoples contradicts Genesis. ⚙ We think the two senses are not rivals so much as layers: the man is named, and his name means the far side. Matthew Henry, commenting on the whole span from 1:1 to 1:27, sets the frame for both, noting that the original of the Jewish nation is traced from the first man God created, and that when compared with other places there are differences found, yet we must not therefore stumble at the word.

Read under Sola Scriptura — this tool’s own fallible reading (⚙)

⚙ This is the tool's own fallible reading, offered to be tested. A verse like this one is where Scripture is least entertaining and most load bearing. It makes no argument, contains no command, and moves the story forward by exactly two men. But everything that Christian faith claims about God working in actual history rather than in ideas rests on lines like this being the kind of thing that can be written down at all. Two verbs, both yālaḏ, both perfect, both completed. Two object markers insisting these were particular men and not symbols of migration patterns. The Chronicler wrote for returned exiles who needed to know they were still the same people who had been promised something, and he answered them with names. We read the gap over Cainan the same way: the line is real enough to have joints, and a genealogy that had been invented to prove a point would not have joints that its own later witnesses argue about. Henry's word is the one to end on, that the things necessary to salvation are plain enough. The pullquote below is our sentence, not a verse of Scripture.

God keeps His covenant by keeping a list, and the list has real joints in it.

Canonical Threads — out to the whole of Scripture

cross-refs · verify

AI-generated connections. Each carries a verification badge with a recorded basis; contested links are flagged.

The verse the Chronicler was copying: Genesis 10:24 verbal / quotation: confirmed

1 Chronicles 1:18 and Genesis 10:24 share all three proper names and the same verb in the same order. The Verifier records three shared Hebrew lexemes for this pair: H7974 Shelach, H5677 ʻÊbêr and H775 ʼArpakshad. K&D states the relationship directly, that the register of seventy-one persons and tribes descended from Shem, Ham and Japhet has been taken from Genesis 10, and that this is placed beyond doubt by the exact correspondence of names and by the identical plan and form of both registers; he adds specifically that 1 Chronicles 1:18 is connected by yālaḏ as in Genesis 10:24. This is not allusion. It is reproduction of a source text within the Hebrew canon.

Genesis 10:24

basis: Verifier: three shared Hebrew lexemes, H775 ʼArpakshad (in 9 vv), H7974 Shelach (in 7 vv), H5677 ʻÊbêr (in 15 vv), all rare, occurring together in the same clause order with the same verb H3205 yâlad; K&D independently attests the Chronicler's dependence on Genesis 10

The same names, a different genre: the Shem toledot of Genesis 11 structural / thematic: confirmed

Genesis 11:12 to 11:15 walks the identical sequence, Arphaxad to Shelah to Eber, but in a different literary form: each generation is given an age at begetting and a remainder of years. The Verifier records H7974 Shelach with H775 ʼArpakshad shared at Genesis 11:12 and 11:13, and H7974 with H5677 ʻÊbêr at 11:14 and 11:15. ⚙ We tier this structural rather than verbal because the Chronicler is not reproducing these verses; he is reproducing Genesis 10:24, which says the same thing without the chronology. The relationship between the two Genesis passages, and the fact that the Septuagint of Genesis 11 carries a Cainan the Masoretic text does not, is exactly the ground on which JFB and Poole differ over this verse.

Genesis 11:12 · Genesis 11:13 · Genesis 11:14 · Genesis 11:15

basis: Verifier: shared Hebrew lexemes H7974 Shelach (in 7 vv) and H775 ʼArpakshad (in 9 vv) at Genesis 11:12-13, H7974 with H5677 ʻÊbêr (in 15 vv) at 11:14-15; same succession, different genre and no shared clause structure, so a motif and succession link rather than a quotation

The Chronicler says it twice: 1 Chronicles 1:24 structural / thematic: confirmed

Six verses later the same author restates the same descent in a tighter form at 1 Chronicles 1:24, and the Verifier records H7974 Shelach and H775 ʼArpakshad shared with our verse; 1 Chronicles 1:17 shares H775 and 1 Chronicles 1:19 shares H5677. The chapter thus states the Shem line, expands it into the Joktanite tribes, and then restates the direct line alone in order to reach Abram. ⚙ Read structurally, verse 18 belongs to the expansion and verse 24 to the resumption, which is why Gill can say the posterity of Shem are placed last because from him, in the line of Heber, sprang Abraham.

1 Chronicles 1:17 · 1 Chronicles 1:19 · 1 Chronicles 1:24

basis: Verifier: shared Hebrew lexemes H7974 Shelach (in 7 vv) and H775 ʼArpakshad (in 9 vv) with 1 Chronicles 1:24, H775 with 1:17, H5677 ʻÊbêr (in 15 vv) with 1:19; an internal restatement pattern within one chapter, not a citation

Cainan, and the chain Luke runs the other way flagged: verify source

Luke 3:35-36 runs the same descent in reverse and, in the received Greek text, inserts a Cainan between Arphaxad and Shelah whom the Hebrew of this verse does not name. JFB says Cainan, the father's name, is omitted here and cites Luke 3:36; Poole cites Luke 3:35 and leaves the question open, promising to speak of it in its proper place. ⚙ We flag this link rather than confirm it. The cross is Greek to Hebrew, so no shared Strong's lexeme can be computed and the Verifier offers no basis for it; the very substance of the link, whether the extra generation belongs in the line, is contested between our own two sources and between the Masoretic and Septuagint traditions. It is a real and important connection, but its provenance is disputed and we record it as such.

Luke 3:35 · Luke 3:36

basis: No Verifier basis exists: cross-Testament Greek to Hebrew links cannot share Strong's numbers, so no verbal tier is available. Provenance is genuinely disputed, JFB asserting an omission in the Hebrew while Poole leaves immediate and mediate descent open, and the additional Cainan is absent from the Masoretic text of Genesis 10:24, Genesis 11:12 and this verse

Christ in the Unittypology · verify

AI-generated reading; weigh it against the text.

Why the Chronicler bothered: the line to Abraham, and through Abraham to Messiah ancient/widely-held

Gill gives the redemptive reason for the whole register in his own words: the posterity of Shem are mentioned last, because from him, in the line of Heber, sprang Abraham, the ancestor of the Jewish nation, of whom the Messiah was to come, for whose sake this genealogy is given. Verse 18 is one link of that line, and the last name in it, עֵֽבֶר׃ (‘ê·ḇer, H5677), is the one Geneva ties to the Hebrews themselves. ⚙ Matthew's genealogy opens by calling Jesus the son of Abraham, and Luke's carries the same names through Eber and Shelah and Arphaxad in the other direction. The apostolic conviction is not that Christ arrives from outside history but that He arrives down a documented line, and this verse is two of its joints. This reading is the ancient and widely held one, stated here in Gill's own commentary on the chapter.

Matthew 1:1 · Luke 3:34 · Luke 3:35

One blood, one Adam, one Noah, and the last Adam ancient/widely-held

Matthew Henry, commenting on the whole of 1 Chronicles 1:1-27, draws the conclusion the chapter is built to force: that the nations are now so mingled that no one nation is descended entirely from any single one of these fountains, but that God has created of one blood all nations of men, and they are all descended from one Adam, one Noah; he closes with Malachi's question, have we not all one father, has not one God created us. ⚙ Luke's genealogy runs the very chain our verse belongs to back past Eber and Shem and Noah to Adam, and then names Adam the son of God, before Paul sets Adam as the figure of Him who was to come. The particularity of this verse, two named men in one bloodline, and the universality Henry draws from it are the same doctrine: the Messiah comes to one family precisely in order to reach one race. Widely held, and stated in these terms by Henry on this chapter.

Luke 3:36 · Luke 3:38 · Romans 5:14 · Acts 17:26

The land beyond: Eber's name read toward the call of Abraham novel

Cambridge notes that the Hebrew behind Eber usually means "the land beyond," and wonders whether the name personifies the population beyond the Euphrates. ⚙ If that sense is carried forward, the name at the end of this verse anticipates Joshua's summons to remember that the fathers dwelt on the other side of the River and served other gods, and that God took Abraham from the other side and led him through. The line named here is literally the line of those from beyond, called across. Hebrews describes the same crossing as faith going out toward a city with foundations. We mark this as our own novel extension, not a received reading: K&D would resist the underlying geographic sense of the name, holding with Genesis that Eber is a person, and Geneva derives the Hebrews from the man rather than from the region. The wordplay may be real, but no source in this brief draws the line we have just drawn.

Joshua 24:2 · Joshua 24:3 · Hebrews 11:8

Apparatus & Provenance

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:

  • Cambridge Bible for Schools and Colleges, (1880s)
  • Geneva Study Bible, Marginal Notes (1599)
  • Jamieson, Fausset & Brown, Commentary Critical and Explanatory (1871)
  • Matthew Poole, Annotations upon the Holy Bible (1685)

⚙ Honesty notes for this unit. (1) Only four of the eight commentators in the brief speak to 1 Chronicles 1:18 as such, and we quote those four. Henry's entry is a single block note on 1:1-27, Gill's entry begins at the sons of Japheth and is capped mid sentence, Barnes' entry treats the sons of Shem at 1 Chronicles 1:17 and never reaches verse 18, and K&D's entry is a long general treatment of the whole Genesis 10 parallel. We have cited Henry, Gill and K&D by name in the commentary for claims they actually make about this chapter, and we have not used Barnes at all, because his note is about Uz, Hul, Gether and Meshech and would be misattributed if applied here.

(2) The Cainan question is genuinely unresolved in our sources and we have not resolved it. JFB and Poole disagree on how firmly to hold it and even cite different verses in Luke's chain, Luke 3:36 and Luke 3:35 respectively. The Hebrew before us names two generations, Arphaxad to Shelah to Eber, with no textual variant reported in this brief. Our Luke thread is therefore badged "flagged: verify source."

(3) The Verifier can compute shared lexemes only within one original language, so every cross-Testament link in this unit is tiered structural, typological or flagged, never verbal. The one verbal tier we assign, to Genesis 10:24, rests on three rare shared Hebrew lexemes in identical clause order plus K&D's independent statement that the Chronicler took the register from Genesis 10.

(4) Our third christ entry, reading Eber as "the land beyond" toward Joshua 24, is marked novel and is our own construction. Cambridge supplies only the lexical observation and offers it tentatively; K&D argues against treating these names as anything but persons. Readers should weigh it accordingly.

(5) Word index 6, the second direct object marker, carries no note because it would only repeat the note at index 2.

= 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)