Triple
T38379019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manghit clan |
E893705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Uzbek tribal dynasty |
C28582
|
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: Uzbek tribal dynasty Context triple: [Manghit clan, instanceOf, Uzbek tribal dynasty]
-
A.
Uzbek ruling house
chosen
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.
-
B.
Pashtun dynasty
A Pashtun dynasty is a ruling lineage or royal house originating from the Pashtun ethnic group, historically governing territories in regions such as present-day Afghanistan, Pakistan, and northern India.
-
C.
Turkic ruling house
A Turkic ruling house is a dynastic lineage of Turkic origin that holds political authority over a state or empire, often legitimized through shared ancestry, cultural traditions, and military power.
-
D.
Oghuz Turkic polity
An Oghuz Turkic polity is a socio-political entity formed by Oghuz Turkic groups, typically characterized by tribal confederation structures, nomadic or semi-nomadic lifeways, and rule by military-elite lineages asserting authority over diverse subject populations.
-
E.
Arghun dynasty ruler
An Arghun dynasty ruler is a sovereign from the late medieval Turco-Mongol Arghun family who governed regions of present-day Afghanistan and Pakistan, particularly Sindh and parts of Baluchistan, often blending Persianate, Islamic, and Central Asian political traditions.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.