Triple
T18109815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aryandes |
E433442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian official |
C13304
|
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 official Context triple: [Aryandes, instanceOf, Persian official]
-
A.
Abbasid official
An Abbasid official was a bureaucrat or administrator serving the Abbasid Caliphate, responsible for managing state affairs such as taxation, justice, military logistics, and provincial governance within the empire’s centralized administrative system.
-
B.
Achaemenid noble
chosen
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.
Timurid official
A Timurid official was an administrative or military functionary serving the Timurid Empire, responsible for implementing imperial policies, managing provincial governance, and maintaining order and revenue collection under the authority of the Timurid rulers.
-
D.
Persian military commander
A Persian military commander is a high-ranking leader responsible for planning, directing, and overseeing the armed forces of Persia in warfare and defense operations.
-
E.
Byzantine official
A Byzantine official is a government functionary of the Eastern Roman (Byzantine) Empire responsible for administering imperial policies, finances, justice, or military affairs within its complex bureaucratic hierarchy.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:28 a.m.