Triple
T28754420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qo Xiong |
E731627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hmong-Mien language family member |
C8648
|
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: Hmong-Mien language family member Context triple: [Qo Xiong, instanceOf, Hmong-Mien language family member]
-
A.
branch of Hmongic languages
A branch of Hmongic languages is a subgroup within the Hmongic language family consisting of closely related languages that share a common historical origin and linguistic features.
-
B.
Hmong-Mien language
chosen
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.
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.
-
E.
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.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 6:09 a.m.