Triple
T5260577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ai |
E118812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Book of Joshua |
C16508
|
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: event in the Book of Joshua Context triple: [Battle of Ai, instanceOf, event in the Book of Joshua]
-
A.
event in the Hebrew Bible
chosen
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.
-
B.
Old Testament event
An Old Testament event is a significant occurrence or narrative described in the Hebrew Bible that shapes the religious, historical, and theological context of ancient Israel.
-
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.
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.
-
E.
biblical episode
A biblical episode is a distinct narrative event or scene described in the Bible, typically involving specific characters, actions, and theological significance within the broader scriptural story.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:50 p.m.