Triple
T31580034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karluk territories |
E805796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Turkic-inhabited region |
C59131
|
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: Turkic-inhabited region Context triple: [Karluk territories, instanceOf, Turkic-inhabited region]
-
A.
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.
-
B.
Oghuz Turkic tribe
An Oghuz Turkic tribe is a socio-political and kinship-based group descended from the historical Oghuz Turks, sharing common lineage, language, and cultural traditions within the broader Oghuz Turkic world.
-
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.
Turkic word
A Turkic word is a lexical item belonging to the Turkic language family, characterized by agglutinative morphology, vowel harmony, and shared historical roots across related languages.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:22 p.m.