Triple
T14676335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Timur |
E344656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Timurid dynasty |
C12349
|
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 dynasty Context triple: [House of Timur, instanceOf, Timurid dynasty]
-
A.
Isma'ili dynasty
The Isma'ili dynasty refers to a series of Muslim ruling families and states historically led or influenced by Isma'ili Shi'a communities, most notably the Fatimid Caliphate, which combined religious leadership with political authority.
-
B.
Timurid ruler
chosen
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.
-
C.
Uzbek ruling house
The Uzbek ruling house is the dynastic lineage that held political authority and sovereignty over Uzbek territories, shaping the region’s governance, culture, and historical development.
-
D.
Persianate dynasty
A Persianate dynasty is a ruling family or political regime that, regardless of its ethnic origin, adopts and promotes Persian language, culture, administrative practices, and aesthetic ideals as the core framework of its governance and elite identity.
-
E.
Turco-Mongol
Turco-Mongol refers to the historical synthesis of Turkic and Mongol political, military, and cultural traditions that shaped several Eurasian empires from the medieval to early modern periods.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:27 a.m.