Triple
T10166546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviticus 18:5 |
E235218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | verse in the Book of Leviticus |
C17235
|
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: verse in the Book of Leviticus Context triple: [Leviticus 18:5, instanceOf, verse in the Book of Leviticus]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
event in the Hebrew Bible
An event in the Hebrew Bible is a narrated occurrence—historical, theological, or symbolic—in which God’s purposes unfold through actions, experiences, or interventions in the lives of individuals or communities.
-
E.
section of a religious text
chosen
A section of a religious text is a distinct, thematically or structurally defined subdivision—such as a chapter, verse group, or discourse unit—within a sacred scripture that conveys a coherent portion of its teachings or narrative.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:10 p.m.