Triple
T9778852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karluk languages |
E237314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Turkic language subgroup |
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: Turkic language subgroup Context triple: [Karluk languages, instanceOf, Turkic language subgroup]
-
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.
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 under a common ancestral origin.
-
D.
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.
-
E.
Tungusic language
A Tungusic language is a member of a small family of agglutinative languages spoken primarily in eastern Siberia, northeastern China, and the Russian Far East by Tungusic peoples.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:27 p.m.