Triple
T10433864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dārayavauš |
E245985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Persian personal name |
C4308
|
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: Old Persian personal name Context triple: [Dārayavauš, instanceOf, Old Persian personal name]
-
A.
Persian given name
chosen
A Persian given name is a personal name of Iranian origin, often derived from the Persian language, history, literature, or cultural and religious traditions, used to identify an individual.
-
B.
Persian-language surname
A Persian-language surname is a family name originating from the Persian language and cultural tradition, often reflecting ancestry, geography, occupation, or personal attributes.
-
C.
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.
-
D.
Persian title
A Persian title is an honorific or formal designation used in Persian-speaking cultures to denote social status, nobility, profession, or respect, often preceding or following a person's name.
-
E.
Mesopotamian royal epithet
A Mesopotamian royal epithet is a formal, often formulaic honorific phrase used in inscriptions and texts to define, praise, and legitimize a king’s divine favor, authority, and achievements.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:14 p.m.