Triple
T23506303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodish languages |
E572290
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sino-Tibetan languages subgroup |
C6638
|
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: Sino-Tibetan languages subgroup Context triple: [Bodish languages, instanceOf, Sino-Tibetan languages subgroup]
-
A.
Sino-Tibetan language
chosen
A Sino-Tibetan language is any member of a large language family, including Chinese and Tibeto-Burman languages, characterized by shared historical origins in East and Southeast Asia and often featuring tonal systems and analytic grammar.
-
B.
Tai-Kadai language
A Tai-Kadai language is a member of a family of tonal languages spoken primarily in Southeast Asia and southern China, characterized by similar phonological, lexical, and grammatical features that suggest a common historical origin.
-
C.
Munda languages subgroup
The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
-
D.
Austronesian subgroup
An Austronesian subgroup is a classification of related languages within the Austronesian language family that share common historical origins and linguistic features.
-
E.
Southwestern Tai languages subgroup
The Southwestern Tai languages subgroup comprises a branch of the Tai language family spoken primarily in mainland Southeast Asia, including Thai, Lao, and related regional languages that share common historical and linguistic features.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:07 p.m.