The sons of Asher, and the heads among his children
아셀의 아들들과 그 자손의 족장들
1 Chronicles 7:30–40: the text opens, “The sons of Asher: Imnah, Ishvah, Ishvi, and Beriah. Serah was their sister.” It names the sons of Beriah, “Heber and Malchiel, who was the father of Birzaith” (7:31); 7:32–39 name the children Heber became the father of and the sons of Japhlet, Shemer, Helem, Zophah, Jether and Ulla; and 7:40 closes, “All these were the children of Asher, heads of the fathers’ houses, choice and mighty men of valor, chief of the princes. The number of them listed by genealogy for service in war was twenty-six thousand men.” The Korean Revised Version writes one name, 소멜, where WEB reads Shomer (7:32) and Shemer (7:34).
Direct relationships 0
Open in the full graphNo relationship is recorded yet.
Collected relationship evidence
Source-backed narrative relations; not independent historical verification. Legacy dates and coordinates are outside this review.
Collection & rightsSource evidence (1)
AI-assisted comparison with the cited narrative; not independent historical verification.
- 1CH 7:30–40, engwebp
30The sons of Asher: Imnah, Ishvah, Ishvi, and Beriah. Serah was their sister.
31The sons of Beriah: Heber and Malchiel, who was the father of Birzaith.
32Heber became the father of Japhlet, Shomer, Hotham, and Shua their sister.
33The sons of Japhlet: Pasach, Bimhal, and Ashvath. These are the children of Japhlet.
34The sons of Shemer: Ahi, Rohgah, Jehubbah, and Aram.
35The sons of Helem his brother: Zophah, Imna, Shelesh, and Amal.
36The sons of Zophah: Suah, Harnepher, Shual, Beri, Imrah,
37Bezer, Hod, Shamma, Shilshah, Ithran, and Beera.
38The sons of Jether: Jephunneh, Pispa, and Ara.
39The sons of Ulla: Arah, Hanniel, and Rizia.
40All these were the children of Asher, heads of the fathers’ houses, choice and mighty men of valor, chief of the princes. The number of them listed by genealogy for service in war was twenty-six thousand men.
AI-assisted, human review pending, 2026-09-26
Machine comparison on 2026-10-07: the wording raised none of the 3 rules against the passages this entry cites. No person has read it.
Verses tagged with this entry
Names in the World English Bible text that carry this entry’s tag. They are carried over from the tags on the Korean Revised Version, which are matched by name inside chapters that already have collected evidence, and a verse where the English says “he” carries none. All await human review. They are a separate list from the source passages above. An empty list does not mean the entry is absent from the text.
No verse carries this tag yet.
Something looks wrong in this entry?
This prepares a report carrying the entry, what it currently says and what it cites, so a reviewer can act on it. Nothing leaves this page until you press Send; the operator alone reads what you send.
Write what looks wrong first; a report without it cannot be acted on.
This is exactly what gets copied or sent:
[Bibliadatum entry report]
Entry: The sons of Asher, and the heads among his children (event-1ch-7-the-sons-of-asher)
Address: https://bibliadatum.org/en/wiki/event/1ch-7-the-sons-of-asher
Current wording: 1 Chronicles 7:30–40: the text opens, “The sons of Asher: Imnah, Ishvah, Ishvi, and Beriah. Serah was their sister.” It names the sons of Beriah, “Heber and Malchiel, who was the father of Birzaith” (7:31); 7:32–39 name the children Heber became the father of and the sons of Japhlet, Shemer, Helem, Zophah, Jether and Ulla; and 7:40 closes, “All these were the children of Asher, heads of the fathers’ houses, choice and mighty men of valor, chief of the princes. The number of them listed by genealogy for service in war was twenty-six thousand men.” The Korean Revised Version writes one name, 소멜, where WEB reads Shomer (7:32) and Shemer (7:34).
Cited evidence: 1CH 7:30–40, engwebp
Review state: ai-assisted / human-review-pending
What looks wrong:
(not written yet)
---
This collection records what the text says and does not settle interpretation. A report about a reading that divides opinion may be registered as an unresolved issue rather than corrected.