Triple
T1151757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belshazzar |
E23691
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in the Book of Daniel |
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 Book of Daniel Context triple: [Belshazzar, instanceOf, character in the Book of Daniel]
-
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.
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.
-
D.
figure in Jewish tradition
A figure in Jewish tradition is an individual—historical, legendary, or symbolic—who plays a significant role in Jewish religious texts, narratives, law, or cultural memory.
-
E.
church mentioned in the Book of Revelation
A church mentioned in the Book of Revelation is a Christian congregation or community addressed in Revelation’s letters, symbolizing both a historical local assembly and a spiritual type with specific strengths, weaknesses, and prophetic significance.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:44 p.m.