Triple
T5361597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeastern Turkic |
E103033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Turkic language family |
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: branch of the Turkic language family Context triple: [Northeastern Turkic, instanceOf, branch of the Turkic language family]
-
A.
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.
-
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.
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.
-
D.
branch of Austroasiatic languages
A branch of Austroasiatic languages is a subgroup within the Austroasiatic language family whose member languages share a common historical origin and distinctive linguistic features.
-
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 under a common ancestral origin.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 2:02 p.m.