Triple
T19629506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagoas the eunuch |
E471228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian court official |
C42284
|
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 court official Context triple: [Bagoas the eunuch, instanceOf, Persian court 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.
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.
-
C.
Safavid royal consort
A Safavid royal consort was a spouse or favored partner of a Safavid shah who held significant social, political, and cultural influence within the royal court and dynastic affairs of Safavid Iran.
-
D.
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.
-
E.
Mughal official
A Mughal official was an appointed administrator or noble in the Mughal Empire responsible for governing territories, collecting revenue, maintaining law and order, and implementing imperial policies on behalf of the emperor.
- F. None of above. chosen
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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:44 p.m.