Triple
T21248710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Darius |
E523684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Old Testament |
C5606
|
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: character in the Old Testament Context triple: [King Darius, instanceOf, character in the Old Testament]
-
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.
biblical character
chosen
A biblical character is an individual, either historical or symbolic, depicted in the Bible whose actions, experiences, and relationships contribute to the religious, moral, and narrative themes of the scriptural text.
-
C.
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.
-
D.
New Testament character
A New Testament character is an individual—historical, symbolic, or parabolic—who appears in the Christian New Testament writings and contributes to its theological, narrative, or moral themes.
-
E.
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.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:56 p.m.