Triple
T30478824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoa Binh Muong |
E775518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Muong language |
C57050
|
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: regional variety of the Muong language Context triple: [Hoa Binh Muong, instanceOf, regional variety of the Muong language]
-
A.
Miao language variety
A Miao language variety is a specific regional or social form of the Miao (Hmongic) language, distinguished by its unique phonological, lexical, and grammatical features within the broader Miao language family.
-
B.
regional variety of Jingpo language
A regional variety of the Jingpo language is a geographically or socially distinct form of Jingpo characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Jingpo varieties.
-
C.
Zhuang language variety
A Zhuang language variety is a specific regional or social form of the Zhuang language, characterized by distinct phonological, lexical, and grammatical features within the broader Tai language continuum.
-
D.
regional variety of the Kayan language
A regional variety of the Kayan language is a geographically distinct form of Kayan characterized by unique phonological, lexical, or grammatical features shared by speakers in a particular area.
-
E.
regional variety of Siwu language
A regional variety of the Siwu language is a geographically and socially distinct form of Siwu characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Siwu-speaking areas.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:12 p.m.