Triple
T4748257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exodus 13:16 |
E105414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | verse in the Book of Exodus |
C16297
|
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 Exodus Context triple: [Exodus 13:16, instanceOf, verse in the Book of Exodus]
-
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.
Exodus narrative element
An Exodus narrative element is a story component that depicts the journey from oppression or bondage toward liberation and covenantal identity, often marked by divine intervention, conflict with oppressive powers, and transformative passage through liminal spaces.
-
C.
location mentioned in the Hebrew Bible
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.
-
D.
artifact described in the Hebrew Bible
An artifact described in the Hebrew Bible is any physical object, tool, structure, or item mentioned within the biblical texts that holds religious, cultural, or historical significance in the narrative of ancient Israel.
-
E.
Biblical chapter
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.
- F. None of above. chosen
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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.