person · also Jair

Jaare-oregim

יַעֲרֵי אֹרְגִים

Jaare-oregim (or Jair) was the father of Elhanan, who killed Lahmi, the brother of Goliath the Gittite.

verses
2
first named
2 Samuel 21:19
last named
1 Chronicles 20:5
period
United Monarchy
role
Warrior

Description

Who was Jaare-oregim?

In the words of STEPBible TIPNR:

Jaare-oregim, also known as Jair, is mentioned in two parallel passages (2Sa.21.19 and 1Ch.20.5) as the father of Elhanan, one of David's mighty warriors. The name Jaare-oregim is likely a scribal error or a variant spelling of Jair, as the latter name is used in 1Ch.20.5.

Elhanan, the son of Jaare-oregim (Jair), is credited with killing Lahmi, the brother of Goliath the Gittite, in a battle against the Philistines at Gob. This event is similar to David's famous encounter with Goliath (1Samuel 17), but it involves Elhanan killing Goliath's brother rather than Goliath himself.

The mention of Jaare-oregim (Jair) serves to identify Elhanan and connect him to his father. It also highlights the ongoing conflicts between the Israelites and the Philistines during David's reign and the bravery of David's mighty warriors in these battles.

No other information is provided about Jaare-oregim (Jair) himself, as the focus is on his son Elhanan's achievement. The inclusion of this event in the biblical record demonstrates the importance of individual heroic acts in the larger context of Israel's military history.

Relations

Direct connections

Every entity the graph places in a stated relation with this one, grouped by the kind of link. Each relation is authored once and its inverse derived, so both ends always agree. Rows marked “registry” come from the identity spine rather than from a verse, and a row marked “which bearer is the source’s decision” is one where the name could have meant more than one person. The last group is not a relation at all — it counts the events two entities stand in together.

Places

Where this happens

A person is placed by the events they take part in, and an event has to clear three things to place them: it must say where it happened, that place must be one the gazetteer can put a coordinate on, and the verse must report it rather than foretell, command or ask it. Nothing anchored here clears all three. Where the text names a setting no gazetteer surveys — a vineyard, a palace, a plot of ground — it is left off rather than guessed at; where a place is named only in a prophecy, the map does not draw what was said to be coming as though it had happened; and a place reached only through a relation is not inherited, because standing beside somebody is not being somewhere.

No verse Atlas has read as a report puts this person anywhere.

Not read yet

The pattern

Where Jaare-oregim is named

Every book of the corpus in the order it is read, each as wide as the chapters it holds. A bar is the verses of that book which write the name, and the flat stretches are as much of the answer as the bars.

Where the name is written across the corpus. 2 verses across 2 of 66 books; 64 write the name nowhere. OLD TESTAMENT · 39 BOOKSNEW TESTAMENT · 27 BOOKS2 SAMUEL1 VERSE53 books and 822 chapters with no mentionBOOK WIDTH = CHAPTER COUNT Where the name is written across the corpus. 2 verses across 2 of 66 books; 64 write the name nowhere. OT · 39 BOOKSNT · 27 BOOKS2 SAMUEL1 VERSE53 books with no mentionBOOK WIDTH = CHAPTER COUNT

2 verses across 2 of 66 books; 64 write the name nowhere. Named in 2 Samuel (1) and 1 Chronicles (1).

Jaare-oregim is named in 2 verses — occurrences of the name in the Hebrew or Greek, counted in the versification of the Berean Standard Bible (v5.7). Every book of the corpus is drawn, its width its share of the 1,189 chapters. 64 of the 66 books never write it. A verse that tells of this subject without writing the name is not counted here.

Read it

Where to read it

Every verse of the text carried here that names this entity — 2, across 2 books.

  1. 2 Samuel1 verse

    21:19

  2. 1 Chronicles1 verse

    20:5

Onward

Where this page goes

Nothing in the graph stands one hop from this entity yet. These are the best-connected entities of the same type, so the page still ends somewhere. Descriptions by STEPBible TIPNR.

Sources

What this rests on