Triple
T36304864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kam–Sui |
E893917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kra–Dai language subgroup |
C18738
|
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: Kra–Dai language subgroup Context triple: [Kam–Sui, instanceOf, Kra–Dai language subgroup]
-
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.
Tai-Kadai language
chosen
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.
Sino-Tibetan–Hmong-Mien areal language grouping
Sino-Tibetan–Hmong-Mien areal language grouping refers to a proposed set of contact-based linguistic similarities shared by Sino-Tibetan and Hmong-Mien languages in East and Southeast Asia, arising from long-term geographic proximity and interaction rather than common genetic origin.
-
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 classifiers.
-
E.
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.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.