Triple
T12037451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pishon |
E286577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river in the Book of Genesis |
C14559
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: river in the Book of Genesis Context triple: [Pishon, instanceOf, river in the Book of Genesis]
-
A.
character in the Book of Genesis
A character in the Book of Genesis is an individual—divine, human, or other—who participates in the foundational narratives of creation, covenant, ancestry, and early human history as recorded in the first book of the Hebrew Bible.
-
B.
location mentioned in the Hebrew Bible
chosen
A "location mentioned in the Hebrew Bible" is any geographically identifiable place—such as a city, region, landmark, or territory—explicitly referenced within the canonical texts of the Hebrew Scriptures.
-
C.
verse in the Book of Exodus
A verse in the Book of Exodus is a discrete, numbered textual unit that conveys a specific event, command, dialogue, or narrative detail within the broader account of Israel’s deliverance from Egypt and covenant formation with God.
-
D.
distributary of the Nile
A distributary of the Nile is a branch of the river that diverges from the main channel in its delta region, carrying water and sediment toward the Mediterranean Sea.
-
E.
Mesopotamian creation epic
A Mesopotamian creation epic is a mythological narrative poem that explains the origins of the cosmos, gods, and human society in ancient Mesopotamia, often emphasizing divine conflict and the establishment of cosmic order.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.