Triple
T21248708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Darius |
E523684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian ruler in the Book of Daniel |
C4222
|
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: Persian ruler in the Book of Daniel Context triple: [King Darius, instanceOf, Persian ruler in the Book of Daniel]
-
A.
Achaemenid ruler
chosen
An Achaemenid ruler is a monarch of the ancient Persian Achaemenid Empire who exercised centralized authority over a vast, multicultural territory through a system of satrapies, royal roads, and imperial administration.
-
B.
Neo-Babylonian king
A Neo-Babylonian king is the sovereign ruler of the Neo-Babylonian Empire (c. 626–539 BCE), responsible for military leadership, monumental building projects, religious patronage, and the administration of law and tribute across Mesopotamia.
-
C.
Babylonian nobleman
A Babylonian nobleman is a high-ranking member of ancient Babylonian society who holds political, economic, and social influence through land ownership, administrative roles, and close ties to the royal court.
-
D.
Neo-Babylonian prince
A Neo-Babylonian prince is a royal male heir or close relative of the king in the Neo-Babylonian Empire (c. 626–539 BCE), raised within the courtly, military, and religious traditions that prepared him for governance and dynastic continuity.
-
E.
Sasanian king
A Sasanian king is the sovereign ruler of the Sasanian Empire, wielding supreme political, military, and religious authority over its territories and subjects.
- 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.