Triple
T3439382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuman language |
E72529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kipchak Turkic language |
C7978
|
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: Kipchak Turkic language Context triple: [Cuman language, instanceOf, Kipchak Turkic language]
-
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.
branch of the Turkic languages
chosen
A branch of the Turkic languages is a subgroup of related Turkic languages that share a common historical origin, structural features, and vocabulary within the broader Turkic language family.
-
C.
Oghuz language
The Oghuz language is a member of the Oghuz branch of the Turkic language family, historically spoken by the Oghuz Turks and forming the basis of several modern languages such as Turkish, Azerbaijani, and Turkmen.
-
D.
Uralic language
A Uralic language is a member of the Uralic language family, originating in Northern Eurasia and characterized by features such as agglutinative morphology, extensive case systems, and vowel harmony, including languages like Finnish, Hungarian, and Estonian.
-
E.
Northwest Caucasian language
A Northwest Caucasian language is a member of a small family of indigenous languages spoken in the northwestern Caucasus region, characterized by complex consonant systems, minimal vowel inventories, and rich verbal morphology.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:16 p.m.