Triple
T10666798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior zhuz |
E251377
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of Kazakh zhuzes |
C28822
|
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: component of Kazakh zhuzes Context triple: [Junior zhuz, instanceOf, component of Kazakh zhuzes]
-
A.
Turkic literature
Turkic literature encompasses the oral and written literary traditions produced in Turkic languages across Central Asia, Anatolia, the Caucasus, and surrounding regions, reflecting diverse historical, cultural, and religious influences.
-
B.
Turkic language
A Turkic language is a member of a family of closely related languages spoken across a vast area from Eastern Europe and Anatolia through Central Asia to Siberia and Western China, characterized by agglutinative morphology, vowel harmony, and similar grammatical structures.
-
C.
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.
-
D.
Turkic person
A Turkic person is an individual who identifies with or descends from the diverse ethnolinguistic groups that speak Turkic languages and share related historical and cultural traditions across Eurasia.
-
E.
Aimaq subgroup
Aimaq subgroup refers to a distinct tribal or regional division within the Aimaq people of Afghanistan and neighboring areas, characterized by shared lineage, dialect, and cultural practices.
- F. None of above. chosen
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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:08 p.m.