Triple
T22082516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuming Zhuang |
E545686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tai language variety |
C5794
|
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: Tai language variety Context triple: [Wuming Zhuang, instanceOf, Tai language variety]
-
A.
Tai language
chosen
A Tai language is a member of the Tai branch of the Kra–Dai language family, characterized by tonal phonology and analytic grammar, spoken primarily in Southeast Asia by Tai ethnic groups.
-
B.
Kalinga language variety
A Kalinga language variety is a specific regional or ethnolinguistic form of the Kalinga language spoken in the Cordillera region of the northern Philippines, characterized by distinct phonological, lexical, and grammatical features.
-
C.
Visayan language variety
A Visayan language variety is a specific regional or social form of any language within the Visayan (Bisayan) subgroup of the Austronesian language family, characterized by distinct phonological, lexical, and grammatical features.
-
D.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
E.
Luri language variety
A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:28 p.m.