Triple
T16359252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ‘Arvot Moav |
E397267
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in the Hebrew Bible |
C14559
|
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: location in the Hebrew Bible Context triple: [‘Arvot Moav, instanceOf, location in the Hebrew Bible]
-
A.
location mentioned in the Hebrew Bible
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
verse of the Hebrew Bible
A verse of the Hebrew Bible is a discrete, traditionally numbered textual unit that forms part of the canonical Hebrew Scriptures, often conveying a complete thought, law, narrative detail, or poetic line.
- 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.