Elishah (son of Javan)
엘리사 (야완의 아들)
A name Genesis 10:3–5 lists as a son of Javan.
Direct relationships 1
Open in the full graphCollected relationship evidence
Source-backed narrative relations; not independent historical verification. Legacy dates and coordinates are outside this review.
Collection & rightsSource evidence (2)
AI-assisted comparison with the cited narrative; not independent historical verification.
- 1CH 1:5–7, engwebp
5The sons of Japheth: Gomer, Magog, Madai, Javan, Tubal, Meshech, and Tiras.
6The sons of Gomer: Ashkenaz, Diphath, and Togarmah.
7The sons of Javan: Elishah, Tarshish, Kittim, and Rodanim.
- GEN 10:3–5, engwebp
3The sons of Gomer were: Ashkenaz, Riphath, and Togarmah.
4The sons of Javan were: Elishah, Tarshish, Kittim, and Dodanim.
5Of these were the islands of the nations divided in their lands, everyone after his language, after their families, in their nations.
AI-assisted, human review pending, 2026-09-20
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.
All 1 relationships: AI-assisted, human review pending
-
Javan — Father of — Elishah (son of Javan)
Evidence: 1 Chronicles 1:5–7, Genesis 10:3–5
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.
The sons of Javan were: Elishah, Tarshish, Kittim, and Dodanim.
The sons of Javan: Elishah, Tarshish, Kittim, and Rodanim.
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. The form for sending it is not open yet, so for now the report can only be copied.
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: Elishah (son of Javan) (person-elishah) Address: https://bibliadatum.org/en/wiki/person/elishah Current wording: A name Genesis 10:3–5 lists as a son of Javan. Cited evidence: 1CH 1:5–7, engwebp / GEN 10:3–5, 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.