And the sons of Javan: Elishah, Tarshish, the Kittites, and the Rodanites.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇə·nê yā·wān ’ĕ·lî·šāh wə·ṯar·šî·šāh kit·tîm wə·rō·w·ḏā·nîm
The Fallible · Synthetic · Study Bible
1 Chronicles 1:7–8 — . 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.
And the sons of Javan: Elishah, Tarshish, the Kittites, and the Rodanites.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇə·nê yā·wān ’ĕ·lî·šāh wə·ṯar·šî·šāh kit·tîm wə·rō·w·ḏā·nîm
The sons of Ham: Cush, Mizraim, Put, and Canaan.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
bə·nê ḥām kūš ū·miṣ·ra·yim pūṭ ū·ḵə·nā·‘an
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.
⚙ These two verses contain no verb, no sentence and no event. They are a copy, and the copying is the point. K&D demonstrates it structurally rather than by assertion: the register's dependence on Genesis 10 "is placed beyond doubt" because not only the names but "the plan and form of both registers is quite the same," the sections joined by וּבני in 1 Chronicles 1:5-9 just as in Genesis 10:2-7, shifting to ילד from v. 10 as in Genesis 10:8. What the Chronicler leaves out is as deliberate as what he keeps: K&D lists the omitted introduction and conclusion of Genesis 10 and, strikingly, the whole Nimrod narrative of empire-building in Babel. Pulpit sets the two texts side by side and notes the residue, "Put here for Phut there," Caphthorim for Caphtorim, Girgashite for Girgasite. A post-exilic community with no king and no empire is handed the old map of the nations with the story of the first empire quietly cut out of it.
✦ Cambridge and K&D both reach the end of what evidence allows in v. 7, and both say so. On Elishah, Cambridge cites Ezekiel's "isles of Elishah" addressed to Tyre, concludes that it "clearly denotes some islands or coastlands near the territory of Javan," and then halts: "no closer identification is at present possible." On the final name, K&D places רודנים here against דּדנים at Genesis 10:4 among divergences arising from errors of transcription, and judges that it "cannot with certainty be determined which form is the original and correct one." Cambridge is bolder, following Hebrew and LXX (Ῥόδιοι) to the Rhodians. Barnes, characteristically, refers the reader to Genesis and writes nothing. ⚙ Four commentators, one disputed consonant, and no consensus: the honest study note here is the disagreement itself, not a decision imposed on it.
⚙ Read forward, this roll of sons is a roll of adversaries and trading partners. Cambridge traces Kittim from Citium in Cyprus to the point where "the ships of Kittim" in Daniel 11:30 are Roman ships. Ellicott and Cambridge together identify Cush with the Ethiopia of the Assyrian inscriptions and Mizraim with Egypt, and Cambridge notes that Put stands "among the helpers of Egypt" in Jeremiah, Ezekiel and Nahum. The Verifier's shared-lexeme candidates confirm the pattern inside Scripture rather than outside it: H6316 Pûwṭ, a rare word found in seven verses, recurs at Nahum 3:9, Jeremiah 46:9, Ezekiel 30:5, Ezekiel 38:5 and Ezekiel 27:10, and in nearly every case beside H3568 Kûwsh. ✦ Against that, Henry holds the line the other way: the nations are now so mingled that no people descends entirely from any one of these fountains, and "God has created of one blood all nations of men." The list is a genealogy of enemies and a genealogy of kin, and Scripture will not let either reading cancel the other.
⚙ This is the tool's own fallible reading, offered to be tested. Two verses of pure nomenclature are the hardest place in Scripture to fake devotion, and that is their value. Nothing here can be made edifying by force: the text gives a Cypriot coastland, a Cilician or Spanish port, an island of ships, a disputed consonant, and then four names that will become Ethiopia, Egypt, a mercenary people and a cursed land. What the passage asserts is simply that these belong on the same page as Israel, written by the same hand. ✦ Gill argues that the whole genealogy is ordered toward one end, Shem placed last "because from him, in the line of Heber, sprang Abraham," and Henry insists the same book that traces Israel from the first man refuses to let Israel stand apart from the rest. ⚙ Our reading takes both seriously and claims no more than they allow: the Chronicler does not moralize these nations, does not curse them here, and does not explain them. He records them. A people rebuilding a ruined temple is first shown the whole earth, and only afterward its own line through it. Where the evidence runs out, as at Elishah and at Rodanim, we have said so rather than filled the gap, on the conviction that a stated uncertainty is worth more to a reader than a confident guess.
Before the Chronicler tells Israel who Israel is, he makes Israel read the names of everyone else.
AI-generated connections. Each carries a verification badge with a recorded basis; contested links are flagged.
⚙ This verse is not merely similar to Genesis 10:4; it is that verse recopied, with two spelling changes. K&D: the register "has been taken from Genesis 10 ," proved by the exact correspondence of names and by the identical plan and connectors of both lists. The Verifier records three shared lexemes across the pair, including one that is genuinely rare in the canon. The two divergences are the he on Tarshishah and the R/D of Rodanim, both of which K&D discusses and neither of which he resolves.
Genesis 10:4
basis: Verifier: shared Hebrew lexemes H473 ʼĔlîyshâh (rare, in 3 vv), H8659 Tarshîysh (in 24 vv), H3120 Yâvân (in 11 vv); K&D states the register is taken from Genesis 10, so this is transcription of a source text, not merely a shared motif
✦ Cambridge supplies the only prophetic use: Ezekiel, addressing Tyre, names "Blue and purple from the isles of Elishah" as the source of her awning. ⚙ H473 occurs in three verses in all, so this pairing is close to the whole canonical life of the word. What the genealogy files as a son, Ezekiel treats as a maritime source of dyed cloth for a merchant city, which is why Cambridge concludes only that Elishah denotes islands or coastlands near Javan and declines to identify them further.
Ezekiel 27:7
basis: Verifier: shared Hebrew lexeme H473 ʼĔlîyshâh, rare at 3 verses in the canon; a real lexical link, though Ezekiel is not citing Chronicles, so the shared word and not a quotation is the whole of the basis
⚙ As with v. 7, v. 8 stands over its Genesis original. Pulpit sets the parallel out explicitly, "The parallel list is found in Genesis 10:6-20 ," and catalogues the small differences, "e.g. Put here for Phut there." He also notes what Chronicles drops: the Nimrod material and the closing statement about the spreading of the Canaanite families and their borders. The Chronicler keeps the four names and removes the commentary.
Genesis 10:6
basis: Verifier: shared Hebrew lexemes H6316 Pûwṭ (in 7 vv), H3568 Kûwsh (in 30 vv), H3667 Kᵉnaʻan (in 91 vv); Pulpit and K&D both identify Genesis 10:6-20 as the source list, so the link is textual dependence
⚙ The two names stand side by side in v. 8 with no comment. In the prophets they stand side by side as allied troops: the Verifier returns Nahum 3:9, Jeremiah 46:9, Ezekiel 30:5 and Ezekiel 38:5, each sharing both lexemes with this verse. ✦ Cambridge notes the same pattern from the other end, that Put "is mentioned among the helpers of Egypt in Jer., in Ezek. (twice) and in Nahum," and in Ezekiel 27:10 among the auxiliary troops of Tyre. No prophet is quoting Chronicles; the recurrence is of the peoples, not of a text.
Nahum 3:9 · Jeremiah 46:9 · Ezekiel 30:5 · Ezekiel 38:5 · Ezekiel 27:10
basis: Verifier: shared Hebrew lexemes H6316 Pûwṭ (in 7 vv, rare) and H3568 Kûwsh (in 30 vv) across all four prophetic refs; the shared words are proper names of peoples recurring in a common motif of coalition, which supports a thematic and not a quotation claim
✦ Cambridge argues that Tarshish here is likely Tarsus in Cilicia precisely because "the next people mentioned are its near neighbours, the Kittim," and he lists the later occurrences of Kittim at Numbers 24:24, Isaiah 23:1 and 23:12, Jeremiah 2:10, Ezekiel 27:6 and Daniel 11:30, adding that "in later times Kittim (Chittim) is used vaguely of Western nations" and that Daniel's "ships of Kittim" are Roman ships. ⚙ Isaiah 23:1 holds both of this verse's names together in a single oracle against Tyre. The genealogy gives the names; the prophets give them a history.
Isaiah 23:1 · Numbers 24:24 · Daniel 11:30 · Jeremiah 2:10
basis: Verifier: shared Hebrew lexemes H3794 Kittîy (in 8 vv) and, at Isaiah 23:1, H8659 Tarshîysh (in 24 vv); a genuine lexical overlap, but the prophetic texts develop the names independently rather than citing the register, so the tier is thematic
⚙ Isaiah 66:19 shares two of v. 7's names with it, Tarshish and Javan, and places them among the far coastlands to which survivors are sent to declare God's glory among the nations. The list of peoples in the Chronicler's opening and the list of destinations in Isaiah's closing vision are drawn from the same stock of names. We claim no citation in either direction, only that the same geography is in view.
Isaiah 66:19 · Ezekiel 27:13
basis: Verifier: shared Hebrew lexemes H8659 Tarshîysh (in 24 vv) and H3120 Yâvân (in 11 vv) at Isaiah 66:19, H3120 at Ezekiel 27:13; shared names within a shared motif of distant nations, with no quotation claimed in either direction
✦ Henry draws the table of nations to a single conclusion, that the nations are now so mingled that none descends entirely from one of these fountains, and that "God has created of one blood all nations of men; they are all descended from one Adam, one Noah," closing with Malachi 2:10. ⚙ Paul at the Areopagus reasons from the same premise to the same end, and Revelation's vision of a multitude from every nation, tribe, people and tongue is the list of 1 Chronicles 1 read as a future. This is a thematic reading and is offered as one: no shared Strong's number can exist between a Hebrew genealogy and a Greek sermon, and Henry's phrase is his own summary, not a quotation of Acts.
Malachi 2:10 · Acts 17:26 · Revelation 7:9
basis: Cross-Testament, so no shared Strong's lexeme is possible and no verbal tier is available; the recorded basis is the shared motif of a single common ancestry for all nations, stated for this passage by Henry (who himself cites Malachi 2:10) and not a quotation link
✦ JFB states the ground plainly: the three sons are enumerated partly because "the fulfilment of Noah's prophecy (Ge 9:25-27) could not otherwise appear to have been verified." Cambridge sharpens the oddity of v. 8 against that prophecy: "In Genesis 9:25-27 'Canaan' is not the son of Ham, but takes Ham's place among the sons of Noah." ⚙ The Chronicler records Canaan flatly under Ham and says nothing of the curse. We note the tension rather than resolve it, and we flag the provenance question: the curse text is disputed in its scope and has been gravely misapplied in later history, so the link between this name and Genesis 9 should be checked against the primary texts by any reader who uses it.
Genesis 9:25-27
basis: The Verifier returns no shared-lexeme candidate for Genesis 9:25-27 with these verses; the connection rests on JFB's and Cambridge's editorial claim about why the list exists, and the interpretation of that curse is contested, so provenance is flagged rather than confirmed
AI-generated reading; weigh it against the text.
✦ Gill states the ordering principle of the whole chapter: Japheth first, then Ham, "then of Shem, whose posterity 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." ⚙ On that reading vv. 7 and 8 are the nations set aside in order, so that the line the Chronicler is actually tracing can be reached last and alone. The evangelists take up the same method of naming: Matthew opens his Gospel with a genealogy and Luke runs his back past Abraham to Adam, the very point from which Henry says this chapter begins. The list is archival because the promise is genealogical.
Matthew 1:1 · Luke 3:38
⚙ Tarshish, Javan, the Kittim and the Rodanim are, in v. 7, only names under Japheth. Isaiah 66:19, which shares Tarshish and Javan with this verse by the Verifier's count, sends messengers to those same far coastlands to declare God's glory among nations that have not heard it. Read canonically, the register of the nations is the field into which the gospel is later sent, and the multitude of Revelation 7:9 is that field gathered in. This is the ancient missionary reading of the table of nations; what is ours, and offered as fallible, is the observation that the connection here is lexical and not merely sentimental, since two of the four names in v. 7 recur in Isaiah's sending.
Isaiah 66:19 · Revelation 7:9
⚙ Cush and Put enter Scripture here as two words in a list and reappear, as Cambridge and the Verifier both show, only ever as Egypt's auxiliaries in the oracles of judgment. Yet the Psalms and the prophets also foresee Cush stretching out her hands to God, and Acts records an Ethiopian official reading Isaiah and being baptized. ✦ Henry's premise supports the movement: one blood, one Adam, one Noah, therefore no name on this list is outside the reach of the promise. ⚙ We mark this reading as ours and as figural: the text of v. 8 says none of it, and the link runs through the shared names rather than through any statement of the Chronicler.
Psalm 68:31 · Acts 8:27 · Isaiah 19:24-25
✦ JFB reads the genealogy as the evidence by which Noah's prophecy in Genesis 9:25-27 is seen to be verified, and Canaan stands in v. 8 as the name that prophecy fell on. ⚙ The New Testament's answer to a curse resting on a line is not a better genealogy but a substitution: Christ redeems from the curse by becoming a curse. We hold this deliberately loosely. The Chronicler mentions no curse, the scope of Genesis 9 is disputed among interpreters, and the passage has been put to appalling use in later centuries, so we present this as a figural reading to be tested and not as the plain sense of v. 8.
Genesis 9:25-27 · Galatians 3:13
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: BSB (CC0) with the Berean interlinear and Strong's tagging; commentary quoted verbatim from public-domain sources named by tag.
Two real textual problems sit inside these two verses. First, וְרוֹדָנִים in v. 7 is tagged to H1721, whose Strong's headword is Dôdânîym; the Hebrew here reads R where Genesis 10:4 reads D. K&D classes this among errors of transcription and states that it cannot with certainty be determined which form is original; Cambridge follows Hebrew and LXX to the Rhodians. We have recorded both and decided neither. Second, וְתַרְשִׁישָׁה carries a final he absent from Genesis 10:4, which K&D explains as a directional ending fused into the name. BSB prints "Tarshish" and the form is invisible in English.
Identifications of Elishah, Tarshish, Kittim, Put and Cush in this unit come from Cambridge, Ellicott and Pulpit, writing in the 1870s and 1880s on the basis of the decipherments then available (Tell-el-Amarna, Esarhaddon and Assurbanipal inscriptions, the Behistun inscription, Egyptian hieroglyphs). Their geography is often still defensible and their chronology frequently is not; Ellicott's dating of Ramses II and his section heading about the sons of Ham both belong to their period rather than to the text. Where they hedge, notably Cambridge on Elishah, we have kept the hedge.
Strong's gloss for H3120 in the lexicon supplied to us reads "the name of a son of Joktan, and of the race (Ionians)"; the Chronicler's own context places Javan under Japheth, and we have not resolved that discrepancy in the source lexicon beyond noting it here.
Thread bases are Verifier-computed shared Strong's lexemes with canonical frequencies, quoted in each badge. The Genesis 9:25-27 link and the cross-Testament threads carry no such basis and are tiered accordingly: flagged and structural respectively. Two of the four christ entries are marked novel because the text of these verses makes no messianic statement of any kind; only Gill's account of why the genealogy was recorded is a sourced claim, and it is his.
✦ = 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)