Triple
T38399162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Zhuz |
E900847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kazakh tribal union |
C28820
|
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: Kazakh tribal union Context triple: [Great Zhuz, instanceOf, Kazakh tribal union]
-
A.
Kazakh zhuz
chosen
A Kazakh zhuz is a traditional socio-political and territorial division of the Kazakh people, historically comprising three main confederations (Senior, Middle, and Junior) that organized clans for defense, governance, and nomadic life.
-
B.
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.
-
C.
Kazakh tribe
A Kazakh tribe is a traditional social and kinship group within the Kazakh people, historically organized around shared ancestry, territory, and cultural practices.
-
D.
Tatar khanate
The Tatar khanate is a historical political entity ruled by Tatar khans, typically emerging from the fragmentation of larger steppe empires and characterized by a nomadic or semi-nomadic elite, Turkic-Mongol cultural influences, and control over key trade and military routes.
-
E.
Khitan state
The Khitan state refers to the political entities established by the Khitan people of Northeast Asia, most notably the Liao dynasty (907–1125), which ruled over a multiethnic empire spanning parts of modern China, Mongolia, and Korea.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.