Triple
T7375151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kara-Khanid Khanate |
E170105
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Turkic Muslim dynasty |
C11026
|
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: medieval Turkic Muslim dynasty Context triple: [Kara-Khanid Khanate, instanceOf, medieval Turkic Muslim dynasty]
-
A.
Muslim dynasty
chosen
A Muslim dynasty is a ruling family or lineage that governs a territory or state over successive generations under Islamic political, cultural, and religious principles.
-
B.
Berber Muslim dynasty
A Berber Muslim dynasty is a ruling family or lineage of Berber origin that governed a region within the Islamic world, combining indigenous Amazigh (Berber) cultural elements with Islamic political and religious authority.
-
C.
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.
-
D.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:07 p.m.