Triple
T31269247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Numbers 22–24 |
E797337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of the Book of Numbers |
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: section of the Book of Numbers Context triple: [Numbers 22–24, instanceOf, section of the Book of Numbers]
-
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.
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.
-
D.
section of the New Testament
A section of the New Testament is a distinct, thematically or structurally unified portion of the Christian scriptures that contributes to the overall narrative, teaching, or theological message of the New Testament canon.
-
E.
part of Mishneh Torah
A part of Mishneh Torah is a distinct legal section within Maimonides’ comprehensive codification of Jewish law, addressing a specific thematic area of halakhic practice or belief.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:13 p.m.