Triple
T4216479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darius III |
E94229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | King of Kings of the Achaemenid Empire |
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: King of Kings of the Achaemenid Empire Context triple: [Darius III, instanceOf, King of Kings of the Achaemenid Empire]
-
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.
Achaemenid noble
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
-
C.
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.
-
D.
Shah of Iran
The Shah of Iran was the hereditary monarch and head of state of Iran, wielding supreme political and symbolic authority until the monarchy’s abolition in 1979.
-
E.
ancient Greek ruler
An ancient Greek ruler is a sovereign leader who governed a Greek city-state or kingdom, wielding political, military, and often religious authority within the context of classical Hellenic civilization.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:04 p.m.