Triple
T36304965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maonan language |
E893920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kam–Sui language |
C62530
|
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: Kam–Sui language Context triple: [Maonan language, instanceOf, Kam–Sui language]
-
A.
Kuki-Chin language
A Kuki-Chin language is a member of a subgroup of the Tibeto-Burman language family spoken primarily in northeastern India, Myanmar, and Bangladesh by various Kuki-Chin ethnic communities, characterized by complex phonology and verb morphology.
-
B.
Chamic language
A Chamic language is any member of a subgroup of the Austronesian language family spoken primarily in parts of Vietnam, Cambodia, Thailand, and Hainan, historically associated with the Cham people and related ethnic groups.
-
C.
Khasian language
A Khasian language is a member of the Austroasiatic language family spoken primarily in the Meghalaya region of northeastern India, characterized by its unique phonology, morphology, and syntactic structures distinct from neighboring Indo-Aryan and Tibeto-Burman languages.
-
D.
Chimakuan language
A Chimakuan language is a member of a small family of indigenous languages once spoken in the Pacific Northwest of North America, characterized by complex phonology and verb morphology and now largely endangered or extinct.
-
E.
Kaduic language
Kaduic language is a hypothetical or fictional linguistic system characterized by its unique phonology, grammar, and vocabulary associated with the conceptual culture or species called Kaduic.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.