Triple
T28243952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hmongic languages |
E712109
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sino-Tibetan–Hmong-Mien areal language grouping |
C54582
|
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–Hmong-Mien areal language grouping Context triple: [Hmongic languages, instanceOf, Sino-Tibetan–Hmong-Mien areal language grouping]
-
A.
Sino-Tibetan language
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.
Tibeto-Burman languages subgroup
The Tibeto-Burman languages subgroup is a major branch of the Sino-Tibetan language family comprising hundreds of related languages spoken primarily in the Himalayas, Southeast Asia, and parts of East Asia.
-
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 classifiers.
-
D.
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.
-
E.
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.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11 p.m.