Triple
T31607589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khwarezmian Turkic languages |
E806534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical Turkic language group |
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: historical Turkic language group Context triple: [Khwarezmian Turkic languages, instanceOf, historical Turkic language group]
-
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.
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.
-
D.
Turkic–Iranian mixed language
A Turkic–Iranian mixed language is a contact language that combines core grammatical and lexical features from both Turkic and Iranian language families, typically arising in regions where their speaker communities have long coexisted.
-
E.
Altaic language group (disputed)
The Altaic language group (disputed) is a proposed but widely contested macro-family that would link Turkic, Mongolic, Tungusic, and sometimes Koreanic and Japonic languages based on shared structural and lexical features often argued to result from areal contact rather than common ancestry.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:35 p.m.