Triple
T10321926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chobanids |
E242156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | post-Ilkhanid polity |
C25982
|
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: post-Ilkhanid polity Context triple: [Chobanids, instanceOf, post-Ilkhanid polity]
-
A.
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.
-
B.
Oghuz Turkic polity
chosen
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.
-
C.
Sultanate
A Sultanate is a form of monarchy or state ruled by a sultan, typically characterized by Islamic governance traditions and varying degrees of centralized authority.
-
D.
Central Asian polity
A Central Asian polity is a political entity—such as a state, khanate, emirate, or tribal confederation—centered in the Central Asian region, shaped by its steppe geography, Silk Road connections, and interactions among Turkic, Persian, Mongol, and other cultural influences.
-
E.
Central Asian polity
A Central Asian polity is a historically or contemporarily organized political entity—such as a state, khanate, or empire—centered in the Central Asian region, characterized by its governance structures, territorial control, and interactions with neighboring powers.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:50 a.m.