The descendants of Jeconiah the captive: Shealtiel his son,
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇə·nê yə·ḵā·nə·yāh ’as·sir šə·’al·tî·’êl bə·nōw
The Fallible · Synthetic · Study Bible
The Royal Line After the Exile
1 Chronicles 3:17–24 — The Royal Line After the Exile. 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.
The descendants of Jeconiah the captive: Shealtiel his son,
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇə·nê yə·ḵā·nə·yāh ’as·sir šə·’al·tî·’êl bə·nōw
Malchiram, Pedaiah, Shenazzar, Jekamiah, Hoshama, and Nedabiah.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·mal·kî·rām ū·p̄ə·ḏā·yāh wə·šen·’aṣ·ṣar yə·qam·yāh hō·wō·šā·mā‘ ū·nə·ḏaḇ·yāh
The sons of Pedaiah: Zerubbabel and Shimei. The children of Zerubbabel: Meshullam and Hananiah, their sister Shelomith,
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇə·nê p̄ə·ḏā·yāh zə·rub·bā·ḇel wə·šim·‘î ū·ḇen- zə·rub·bā·ḇel mə·šul·lām wa·ḥă·nan·yāh ’ă·ḥō·w·ṯām ū·šə·lō·mîṯ
and five others: Hashubah, Ohel, Berechiah, Hasadiah, and Jushab-hesed.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ḥā·mêš wa·ḥă·šu·ḇāh wā·’ō·hel ū·ḇe·reḵ·yāh wa·ḥă·saḏ·yāh yū·šaḇ ḥe·seḏ
The descendants of Hananiah: Pelatiah, Jeshaiah, and the sons of Rephaiah, of Arnan, of Obadiah, and of Shecaniah.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇen- ḥă·nan·yāh pə·laṭ·yāh wî·ša‘·yāh bə·nê rə·p̄ā·yāh bə·nê ’ar·nān bə·nê ‘ō·ḇaḏ·yāh bə·nê šə·ḵan·yāh
The six descendants of Shecaniah were Shemaiah and his sons: Hattush, Igal, Bariah, Neariah, and Shaphat.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
šiš·šāh ū·ḇə·nê šə·ḵan·yāh šə·ma‘·yāh šə·ma‘·yāh ū·ḇə·nê ḥaṭ·ṭūš wə·yiḡ·’āl ū·ḇā·rî·aḥ ū·nə·‘ar·yāh wə·šā·p̄āṭ
The sons of Neariah: Elioenai, Hizkiah, and Azrikam—three in all.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇen- nə·‘ar·yāh ’el·yō·w·‘ê·nay wə·ḥiz·qî·yāh wə·‘az·rî·qām šə·lō·šāh
The sons of Elioenai: Hodaviah, Eliashib, Pelaiah, Akkub, Johanan, Delaiah, and Anani—seven in all.
Berean Standard Bible · CC0
Hebrew — tap a word ↓
ū·ḇə·nê ’el·yō·w·‘ê·nay hō·ḏay·wå̄·hū wə·’el·yā·šîḇ ū·p̄ə·lā·yāh wə·‘aq·qūḇ wə·yō·w·ḥā·nān ū·ḏə·lā·yāh wa·‘ă·nā·nî šiḇ·‘āh
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.
The section opens on a word nobody can settle. אַסִּ֔ר (’as·sir, H616) is either a man or a condition. Ellicott, Benson, JFB, Poole, Gill and Cambridge read it as a title and translate, with Ellicott, “the sons of Jeconiah when in captivity”; K&D answers that an appositional title would require the article, and the Pulpit agrees, adding that the Septuagint and Vulgate both take it as a name. The FSSB does not adjudicate. What both readings share is the fact the Chronicler is recording: the line of David continued inside a Babylonian prison. Ellicott notices the corroborating detail one verse later, that Shenazzar is “a compound Babylonian name, like Belteshazzar,” probably invoking the moon god Sin; and in the same breath Hoshama says, on Ellicott's reading, that Iahweh hath heard. Two brothers, one named for a pagan god by the court, one named for the God who hears. That is what exile looks like in a register.
Here the Chronicler's record and the rest of Scripture pull apart. Verse 19 makes Zerubbabel the son of Pedaiah; Ezra 3:2, Haggai 1:1 and Matthew 1:12 make him the son of Shealtiel. The brief's voices offer four different repairs and agree on none: Gill proposes adoption, “Salathiel, having no children, adopted Zerubbabel,” and in the next clause proposes levirate marriage instead; Geneva says flatly that Matthew means nephew “according to the Hebrew speech”; Cambridge floats a double grandson through a daughter, and says outright that “the text of these verses is very uncertain”; JFB, following Davidson, rearranges the verses wholesale. K&D builds the most elaborate reconstruction of all, running Shealtiel's descent through an heiress daughter of Assir married to Neri of Nathan's line. Meanwhile the names themselves are preaching. Ellicott hears in this family's naming “the religious hopefulness of his people at the dawn of the restoration,” and Cambridge translates the last of them, Jushab-hesed, as “Mercy is restored.” The genealogy is uncertain at exactly the point where the names are most confident.
Verse 21 turns on one Hebrew letter. Read with the Masoretic text, Pelatiah, Jeshaiah and four families are Hananiah's sons; read with the Septuagint, which Cambridge judges “probably the LXX. is to be followed,” they are six consecutive generations, and the chapter's last entry falls in the age of Alexander. The Pulpit lays out both and refuses both: the difficulties are “not satisfactorily explained.” Verse 22 then breaks openly. It counts six and lists five. Ellicott concedes that “one must have been omitted by an oversight”; Barnes reports the Syriac and Arabic supplying Azariah, which the Pulpit distrusts since no Hebrew manuscript or Greek or Latin version has it; Poole suggests the Hebrew word for six is itself a name. Against this insecurity stands one solid fact, and Ellicott and the Pulpit both build on it: the Hattush of this verse is very likely the Hattush of the sons of David who returned with Ezra in 457 BC. A damaged list still touches the ground at one known point.
The last two verses are almost nothing but names, and the names are sentences. Ellicott reads Elioenai as “unto Iah ( are ) mine eyes,” Cambridge as “Mine eyes are towards Jehovah,” and pairs it with Jushab-hesed as one house's continued confession. Cambridge reads Hodaviah as “Thank ye Jehovah.” A man whose great-grandfather lost a kingdom names his son give thanks. Then the register stops, on seven sons, the number the lexicon glosses as the sacred full one, and on the name Anani. Gill records that the Targum takes Anani for the King Messiah, on the ground of the clouds of Daniel 7:13, and draws the conclusion that matters whether or not the midrash is sound: the Jews “expected the Messiah to come at the end of this genealogy, and about the time Jesus the true Messiah did.” Benson, four verses earlier, has already said what the whole list is for: it is “recorded in part, to assist us in tracing the descent of our Lord Jesus Christ.” Barnes and Ellicott, for their part, are still arguing about whether the last verse dates to 410 BC or 345 BC. Both concerns are legitimate, and the FSSB prints both.
⚙ This is the FSSB's own fallible reading, offered to be tested. These eight verses are the least impressive passage in the Bible and one of the most load-bearing. There is no throne in them, no oracle, no miracle, not one finished sentence with a verb in it. There is a prisoner, some Babylonian court names, a governor whose paternity nobody can reconcile, a count that comes up one short, and seven great-grandchildren. If God's promise to David depended on visible continuity, it died at v. 17. What the chapter actually shows is a promise being carried by a document: by somebody in Babylon and later in Jerusalem keeping a family register that had no legal force, no crown attached, and, after Jeremiah 22:30, no obvious future. The commentators cannot agree on how the line runs, and their disagreement is itself the point worth noticing. Human transmission of this promise was fragile, partial, contested, and by v. 22 demonstrably damaged. It still got through. And notice what the family did with the only freedom it had left, which was naming: Berechiah, Hasadiah, Jushab-hesed, Pelatiah, Jeshaiah, Elioenai, Hodaviah. Mercy is restored. Iah is salvation. My eyes are toward the LORD. Give thanks. A house that had lost the power to rule kept the power to confess, and spent it on its children. The FSSB reads this list as the quietest evidence in Scripture that God keeps what he promised through means that look, at every point of contact, like they are about to fail.
A genealogy is what a promise looks like when it has to survive an empire. (This line is the FSSB's own reading, not a verse of Scripture.)
AI-generated connections. Each carries a verification badge with a recorded basis; contested links are flagged.
The Igal of v. 22 is written with the same Hebrew word as the Igal who was one of the twelve sent to spy out the land and the Igal who was one of David's mighty men. The Pulpit makes the identification of the word explicit: it is “a word ( יגִךאל ) identical with the Igal of Numbers 13:7 ; 2 Samuel 23:36.” The Verifier confirms the shared lexeme and shows how narrow it is: H3008 occurs in three verses in the whole canon, and these are they. This is a lexical identity, not a quotation and not a claim that the men are related; the tier records the rarity of the shared word, nothing more.
Numbers 13:7 · 2 Samuel 23:36
basis: Verifier: shared rare Hebrew lexeme H3008 Yigʼâl (in 3 vv canon-wide, the only three occurrences); the Pulpit independently notes the Hebrew word is identical. Lexical identity only; no quotation and no claimed relation between the persons.
Pedaiah, Meshullam, Pelaiah, Akkub, Berechiah, Shecaniah, Hananiah and Elioenai are not only names in this register; they are the names of the men standing beside Ezra and Nehemiah a generation or two later, reading the Law aloud, repairing a wall section, sealing a covenant. The Verifier records genuine shared lexemes across these verses. What it cannot record is identity of persons: several of these names are common, and the FSSB makes no claim that the same men are meant. The link is of a milieu, not of a quotation: the Chronicler's closing register and the Nehemiah lists come out of one restored community that named its sons the same way.
Nehemiah 8:4 · Nehemiah 8:7 · Nehemiah 11:7 · Nehemiah 6:18
basis: Verifier: shared Hebrew lexemes H6305 Pᵉdâyâh (in 8 vv), H4918 Mᵉshullâm (in 25 vv), H6411 Pᵉlâyâh (in 3 vv), H6126 ʻAqqûwb (in 8 vv), H1296 Berekyâh (in 11 vv), H7935 Shᵉkanyâh (in 10 vv). Real shared lexemes, but they are personal names, so the basis supports a shared post-exilic milieu and not a verbal dependence.
Ellicott identifies the Hattush of v. 22 with the Hattush of the sons of David who went up with Ezra in 457 BC, and notes that an Elioenai also went up with Ezra. The Verifier finds the Elioenai and Eliashib lexemes shared with the Ezra and Nehemiah lists. This is the only place where this genealogy can be pinned to a datable event, and the Pulpit uses it to argue that v. 21 lists brothers rather than generations. The link is onomastic and prosopographic; the identification of the persons is Ellicott's judgment, which the Pulpit calls a coincidence that “must not be regarded as con-elusive.”
Ezra 8:2 · Ezra 10:27 · Nehemiah 12:41
basis: Verifier: shared Hebrew lexemes H454 ʼElyᵉhôwʻêynay (in 9 vv) and H475 ʼElyâshîyb (in 15 vv) with Ezra 10:27 and Nehemiah 12:41. The Ezra 8:2 Hattush identification is Ellicott's and the Pulpit's judgment, not a Verifier-computed lexeme, and the Pulpit itself declines to call it conclusive.
The Jekamiah of v. 18 shares a name with a Jerahmeelite in 1 Chronicles 2:41, and the Verifier shows the lexeme is confined to those two verses in the entire canon. It is tempting to tier a link that rare as verbal. The FSSB does not, because nothing in the brief connects the two men, they belong to different clans of Judah, and rarity of a proper name is not evidence of literary dependence. The honest statement is narrower: two men in Judah, a few centuries apart, carried a name the rest of Scripture never uses.
1 Chronicles 2:41
basis: Verifier: shared Hebrew lexeme H3359 Yᵉqamyâh (in 2 vv, the only occurrences in the canon). Deliberately not tiered verbal: the rarity is real but the referents are different men in different clans, so the basis supports a lexical curiosity, not a quotation or a dependence.
Every commentator in the brief who touches v. 17 reaches for Jeremiah 22:30. JFB: “Jeconiah was written childless (Jer 22:30), a prediction which (as the words that follow explain) meant that this unfortunate monarch should have no son succeeding him on the throne.” Poole and Gill answer the objection the same way; Cambridge paraphrases the sense as reckoning him childless because no son of his shall succeed him. Barnes takes a harder line, suggesting Assir may have died young or been made a eunuch and the Solomonic line become extinct. The FSSB flags this link rather than confirming it, for two reasons. The Verifier computes no shared lexeme for this pair, so there is no recorded verbal basis. And the meaning of the prophecy is itself contested among the named sources: childless in fact, or childless as to the throne.
Jeremiah 22:30
basis: No Verifier-computed shared lexeme for this pair; the link rests entirely on the named commentators (JFB, Poole, Gill, Cambridge, Barnes), whose readings of the prophecy conflict with one another. Provenance of the connection is commentary, not computed lexeme.
K&D reconciles this chapter with Luke 3:27 by supposing that Assir left only a daughter who, under the law of heiresses, married within her father's tribe, and that her son Shealtiel inherited legally; and reconciles v. 19 with Haggai and Matthew by supposing that Shealtiel died without male issue and that Pedaiah raised up seed to his brother. Benson and Gill reach for the same levirate statute. Barnes invokes the inheritance law of Numbers 27:8-11 to a different end, arguing that the line of Solomon went extinct and the inheritance passed to Nathan's branch. These are legal mechanisms that would explain the data; none of them is stated by the Chronicler. The FSSB flags the link accordingly: the statutes are real, the application here is reconstruction.
Numbers 27:8 · Deuteronomy 25:5
basis: No Verifier-computed shared lexeme with this unit. The connection is a harmonizing reconstruction offered explicitly as a supposition by K&D, and used differently by Barnes, Benson and Gill; it is recorded as the commentators' proposal, not as the text's own claim.
In a list whose entire function is male succession, v. 19 stops to name a woman and mark her relation, אֲחוֹתָֽם׃, sister of them. She is named nowhere else in Scripture, and, as the Pulpit notes, “this person is mentioned here only.” Benson and Poole use her to argue about maternity, that she is full sister to the two named sons and half sister to the five of v. 20. The FSSB notices something simpler and offers it as a structural observation, not a verbal one: the Chronicler's registers repeatedly preserve women who carry no succession value, and that habit is of a piece with the genealogy of Matthew, which will keep four women in a list of fathers. No shared lexeme can be computed across the Testaments here.
Matthew 1:3
basis: Cross-Testament (Greek to Hebrew), so no shared Strong's lexeme is possible and no verbal tier is available. The recorded basis is a shared compositional habit in genealogical lists, that women without succession value are nevertheless entered; stated as a pattern observation, not as a claim of dependence.
AI-generated reading; weigh it against the text.
⚙ The names of vv. 17 and 19 are the names Matthew reaches for when he crosses the exile: Jeconiah, Shealtiel, Zerubbabel. Ellicott notes that the Greek form Salathiel is the one Matthew uses and that Assir is absent from Matthew's list as he is from the Seder Olam; JFB, Poole, Gill, Cambridge and the Pulpit all read this verse with Matthew 1:12 open beside it. K&D and Cambridge wrestle with the harder problem that Luke 3:27 traces Shealtiel through Neri of Nathan's line while Chronicles has him among Jeconiah's sons, and the Pulpit proposes the distinction that has done most of the work since: distinguish the natural descent from the royal descent, and let the royal swallow the natural where necessary. None of those harmonies is certain. What is certain, and is the point here, is that the Evangelists reached into this damaged, disputed, half-legible register when they needed to say who Jesus legally was. The link is cross-Testament and can carry no shared Strong's lexeme; it is the succession of named persons, attested by every commentator in this brief.
Matthew 1:12 · Luke 3:27 · Haggai 1:1
⚙ The last name in David's genealogy is Anani, and Gill records that the Targum identifies him with the King Messiah, since the name carries the sense of clouds and the Son of Man of Daniel 7:13 comes with the clouds of heaven. The FSSB does not endorse that identification: it is a Targumic and later Jewish reading of a name, not an exegesis the Hebrew compels, and Gill reports it rather than asserting it. What survives the caution is Gill's own inference, and it is considerable. The Jewish tradition that produced this reading expected the Messiah at the end of this genealogy, and the genealogy ends within a few centuries of the birth of Jesus. Benson, reading v. 21, says the register was preserved “to assist us in tracing the descent of our Lord Jesus Christ from him, that we might have that proof, among others, of his being the true Messiah.” Matthew Henry says the same of the whole chapter: “From this family, as concerning the flesh, Christ came.” The Targumic identification of Anani is itself ancient, but it is a Jewish reading of a name rather than any Christian exegetical consensus, and the inference drawn here is Gill's own; this entry is therefore marked novel. The Messianic purpose of the register, stated by Benson and Henry, is the widely-held part.
Daniel 7:13 · Matthew 1:13
⚙ Ellicott makes an observation about naming that is worth following further than he takes it. The last kings bore names that were “parables of the judgment,” and the sons of Zerubbabel bear names that are parables of hope: Pedaiah, Iah hath redeemed; Jushab-hesed, which Cambridge renders “Mercy is restored”; Rephaiah, Iah healeth; Pelatiah, Iah is deliverance; Jeshaiah, Iah is salvation; Elioenai, mine eyes are unto Iah; Hodaviah, thank ye Jehovah. Ellicott calls the last of these “a prophecy of faith.” Read as a sequence, this family spent four generations in a landless register confessing that God redeems, heals, delivers, saves, and restores covenant love, with no institutional evidence that he was doing any of it. The FSSB reads this as genuine, if indirect, testimony to Christ: it is the shape of the hope into which he came, kept alive in the only medium a powerless house still controlled. This is the FSSB's own synthesis of Ellicott's and Cambridge's sourced glosses; it is not a claim that any of these names predicts Jesus.
1 Chronicles 3:20 · 1 Chronicles 3:24
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:
⚙ Honesty notes for this unit. 1. The text is damaged and the sources say so. Cambridge: “The text of these verses is very uncertain.” Verse 22 counts six and names five; Ellicott calls it an oversight, Barnes reports a Syriac and Arabic supplement of Azariah which the Pulpit distrusts, Poole suggests the numeral is a name. Verse 19 reads a singular “son” before a plural list; verse 21 reads a singular “son” where the Septuagint read “his son” and produced five extra generations. JFB prints a wholesale rearrangement of vv. 17 to 21 borrowed from Davidson. Nothing in this unit should be treated as a settled stemma.
2. The interlinear token order is not always the order of the Masoretic text. In the Berean data supplied in the brief, the tally words stand first in vv. 20 and 22 (“and five others,” “The six”) though they close the clause in Hebrew, and in v. 19 the token for “their sister” is listed before the token for Shelomith, reversing the Hebrew. The literal renderings above follow the Hebrew order; the note keys follow the brief's token indices, so a note key and the reading order can differ. At v. 20 the first half of the compound name Jushab-hesed (token 5) carries a placeholder gloss and no parse in the source data; the sense belongs to the pair of tokens together.
3. Assir is undecided here on purpose. Six named commentators read it as a title and two read it as a name, and both camps argue from the Hebrew, one from the Masoretic accents and one from the absent article. The FSSB records the split rather than manufacturing a verdict.
4. Dates. Ellicott reckons the last verse to about 345 BC, or about 225 BC on the Septuagint reading of v. 21; Barnes reckons the Hebrew text to about 410 BC and within Nehemiah's lifetime. These are not reconcilable, and both are printed. The FSSB takes no position on the date of the close of the Chronicler's work.
5. Thread bases. Every verbal and structural badge above cites the Verifier's computed shared lexemes. Because this unit is almost entirely proper names, shared lexemes here prove shared names and not shared texts, and every badge says so. Two links carry no computed basis at all, Jeremiah 22:30 and the heiress and levirate statutes, and both are flagged rather than confirmed. Links to Matthew and Luke are cross-Testament and therefore cannot be verbal; they are tiered structural, and their content is the succession of named persons as attested by the commentators, nothing more.
6. Voices. Matthew Henry's entry is a single comment on the whole chapter and appears identically under every verse in the source; it is quoted once. Gill's entry repeats under vv. 19 to 24 in the source; the excerpts used come from the parts of it that bear on the verse in question. The K&D entry is capped in the brief at 8,813 further characters, and the FSSB has quoted only from the portion supplied, so his fuller argument about the Levirate reconstruction is represented in summary from the visible text and not quoted beyond it.
✦ = 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)