Triple
T19576924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasan Khan Sur |
E489881
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Afghan noble |
C41848
|
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: Afghan noble Context triple: [Hasan Khan Sur, instanceOf, Afghan noble]
-
A.
Timurid noble
A Timurid noble is a high-ranking aristocrat within the Timurid Empire, typically of Turco-Mongol lineage, who held land, military command, and administrative authority under the dynasty founded by Timur (Tamerlane).
-
B.
Mongol noble
A Mongol noble is a high-ranking member of Mongol society, typically belonging to ruling or aristocratic lineages, who holds political, military, and economic power within the Mongol Empire or its successor states.
-
C.
Nawab
Nawab: A Nawab is a historical title for a Muslim noble or provincial governor in South Asia, often associated with regional power, landownership, and a refined courtly lifestyle under larger empires such as the Mughals or the British Raj.
-
D.
Chagatai prince
A Chagatai prince is a male royal descendant or member of the ruling family within the Chagatai Khanate, a Mongol successor state founded by Chagatai Khan, son of Genghis Khan, in Central Asia.
-
E.
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.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:42 p.m.