Triple
T13918010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ali-Shir Nava'i |
E334671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Timurid official |
C34370
|
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: Timurid official Context triple: [Ali-Shir Nava'i, instanceOf, Timurid official]
-
A.
Timurid ruler
A Timurid ruler is a sovereign from the Timurid dynasty (14th–16th centuries) who governed territories in Central Asia, Iran, and surrounding regions, often noted for military conquest, Persianate court culture, and patronage of arts and architecture.
-
B.
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.
-
C.
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.
-
D.
Khan of Bukhara
The Khan of Bukhara is the sovereign ruler of the Khanate of Bukhara, a Central Asian polity historically centered in the city of Bukhara and exercising political, military, and religious authority over its territories.
-
E.
Khan of Kokand
The Khan of Kokand was the hereditary ruler of the Kokand Khanate in Central Asia, exercising political, military, and economic authority over the state and its subjects from the 18th to the late 19th century.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.