One other person, place or group in the registry answers to the name Peleth. Every Peleth in the Bible

person

Peleth

פֶּ֫לֶת

Peleth, a son of Jonathan and descendant of Jerahmeel, mentioned in the genealogy of Judah.

verses
1
first named
1 Chronicles 2:33
last named
1 Chronicles 2:33
period
Divided Monarchy
tribe
Judah

Description

Who was Peleth?

In the words of STEPBible TIPNR:

Peleth was a son of Jonathan and a descendant of Jerahmeel, according to the genealogy of Judah in 1Ch.2.33. Jerahmeel was the firstborn son of Hezron, who was a grandson of Judah. Peleth is listed along with his brother Zaza as sons of Jonathan. No further details are provided about Peleth's life or role. His inclusion in the genealogy indicates he was part of the tribe of Judah and lived during the period of Israel's settlement in Canaan or the early monarchy.

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.

How the graph connects Peleth 3 of 3 entities the graph connects to Peleth, in one group: kinship 3. Kinship, company and ground are stated relations; events counts the acts two entities stand in together and is not a relation. Each mark is sized by how many verses name that entity and labelled with the link and the count, so the grouping and the size are both readable without colour. Distance from the centre carries nothing.JerahmeelDescendant of · 8 versesJonathanChild of · 2 versesZazaSibling of · 1 versePeleth

Child of

Descendant of

Sibling of

  • Zazaregistry, no verse

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 Peleth 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. 1 verse across 1 of 66 books; 65 write the name nowhere. OLD TESTAMENT · 39 BOOKSNEW TESTAMENT · 27 BOOKS1 CHRONICLES1 VERSE53 books and 822 chapters with no mentionBOOK WIDTH = CHAPTER COUNT Where the name is written across the corpus. 1 verse across 1 of 66 books; 65 write the name nowhere. OT · 39 BOOKSNT · 27 BOOKS1 CHRONICLES1 VERSE53 books with no mentionBOOK WIDTH = CHAPTER COUNT

1 verse across 1 of 66 books; 65 write the name nowhere. Named in 1 Chronicles (1).

Peleth is named in 1 verse — 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. 65 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 — one, across 1 book.

  1. 1 Chronicles1 verse

    2:33

Onward

Where this page goes

Not the direct relations above — these are one hop further out, ranked so that a rare shared connection outweighs a common one. Descriptions by STEPBible TIPNR.

Sources

What this rests on