The sons of Judah, and the sons of Hur, the firstborn of Ephrathah
유다의 아들들과 에브라다의 맏아들 훌의 소생
1 Chronicles 4:1–4: the text says, “The sons of Judah: Perez, Hezron, Carmi, Hur, and Shobal. Reaiah the son of Shobal became the father of Jahath; and Jahath became the father of Ahumai and Lahad. These are the families of the Zorathites. These were the sons of the father of Etam: Jezreel, Ishma, and Idbash. The name of their sister was Hazzelelponi. Penuel was the father of Gedor and Ezer the father of Hushah. These are the sons of Hur, the firstborn of Ephrathah, the father of Bethlehem.” The Korean Revised Version runs 4:3 on into 4:4, naming Penuel the father of Gedor and Ezer the father of Hushah in the same run as the children of the father of Etam (에담 조상의 자손들은 … 저희의 매제 하술렐보니와 그돌의 아비 브누엘과 후사의 아비 에셀이니), and sets 베들레헴의 아비 (the father of Bethlehem) before 에브라다의 맏아들 훌 (Hur, the firstborn of Ephrathah).
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 4:1–4, engwebp
1The sons of Judah: Perez, Hezron, Carmi, Hur, and Shobal.
2Reaiah the son of Shobal became the father of Jahath; and Jahath became the father of Ahumai and Lahad. These are the families of the Zorathites.
3These were the sons of the father of Etam: Jezreel, Ishma, and Idbash. The name of their sister was Hazzelelponi.
4Penuel was the father of Gedor and Ezer the father of Hushah. These are the sons of Hur, the firstborn of Ephrathah, the father of Bethlehem.
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 Judah, and the sons of Hur, the firstborn of Ephrathah (event-1ch-4-the-sons-of-judah-and-the-sons-of-hur) Address: https://bibliadatum.org/en/wiki/event/1ch-4-the-sons-of-judah-and-the-sons-of-hur Current wording: 1 Chronicles 4:1–4: the text says, “The sons of Judah: Perez, Hezron, Carmi, Hur, and Shobal. Reaiah the son of Shobal became the father of Jahath; and Jahath became the father of Ahumai and Lahad. These are the families of the Zorathites. These were the sons of the father of Etam: Jezreel, Ishma, and Idbash. The name of their sister was Hazzelelponi. Penuel was the father of Gedor and Ezer the father of Hushah. These are the sons of Hur, the firstborn of Ephrathah, the father of Bethlehem.” The Korean Revised Version runs 4:3 on into 4:4, naming Penuel the father of Gedor and Ezer the father of Hushah in the same run as the children of the father of Etam (에담 조상의 자손들은 … 저희의 매제 하술렐보니와 그돌의 아비 브누엘과 후사의 아비 에셀이니), and sets 베들레헴의 아비 (the father of Bethlehem) before 에브라다의 맏아들 훌 (Hur, the firstborn of Ephrathah). Cited evidence: 1CH 4:1–4, 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.