Triple
T22849424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nkhum dialect |
E566315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Jingpo language |
C46916
|
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: variety of Jingpo language Context triple: [Nkhum dialect, instanceOf, variety of Jingpo language]
-
A.
variety of the Naxi language
A variety of the Naxi language is a regional or social form of Naxi distinguished by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Naxi forms.
-
B.
variety of the Zhuang language
A variety of the Zhuang language is a distinct regional or social form of Zhuang characterized by its own phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Zhuang 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.
variety of Fang language
A variety of Fang language is a specific regional or social form of the Fang language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Fang forms.
-
E.
variety of Lepcha language
A variety of Lepcha language is a distinct regional or social form of the Lepcha language characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Lepcha forms.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:36 p.m.