Triple
T3588388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalmyk language |
E75965
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongolic language |
C13413
|
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: Mongolic language Context triple: [Kalmyk language, instanceOf, Mongolic 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.
Hmong-Mien language
A Hmong-Mien language is a member of a small family of tonal languages spoken primarily in southern China and Southeast Asia, characterized by complex phonology and rich systems of classifiers.
-
C.
Hmong-Mien language
A Hmong-Mien language is a member of a small family of tonal languages spoken primarily in southern China and Southeast Asia, characterized by complex phonology and rich systems of lexical tone.
-
D.
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.
-
E.
Munda language
The Munda language is a member of the Austroasiatic language family spoken primarily by indigenous Munda communities in eastern and central India, characterized by agglutinative morphology and distinct phonological features.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.