Triple
T16359176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deuteronomy 34 |
E397265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | chapter of the Book of Deuteronomy |
C6401
|
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: chapter of the Book of Deuteronomy Context triple: [Deuteronomy 34, instanceOf, chapter of the Book of Deuteronomy]
-
A.
verse in the Book of Deuteronomy
A verse in the Book of Deuteronomy is a discrete, numbered textual unit within this biblical book that conveys a specific command, teaching, narrative detail, or theological statement within Moses’ final speeches to Israel.
-
B.
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.
-
C.
Biblical chapter
chosen
A biblical chapter is a numbered division within a book of the Bible that groups related verses into a coherent section of narrative, teaching, poetry, or prophecy.
-
D.
chapter of the Gospel of Matthew
A chapter of the Gospel of Matthew is a sequential division of the biblical text that groups together related narratives, teachings, and events from the life and ministry of Jesus as presented by the evangelist Matthew.
-
E.
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.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.