Triple
T32133634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doteli language |
E820714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Khas language |
C58508
|
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: Khas language Context triple: [Doteli language, instanceOf, Khas language]
-
A.
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.
-
B.
Sambalic language
A Sambalic language is a member of a subgroup of the Austronesian language family spoken primarily by the Sambal and related ethnolinguistic groups in western Central Luzon, Philippines.
-
C.
Malakula language
Malakula language refers to any of the numerous distinct but related indigenous languages spoken on the island of Malakula in Vanuatu, known for their high linguistic diversity and complex phonological and grammatical systems.
-
D.
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.
-
E.
Pearic language
A Pearic language is any member of a small subgroup of Austroasiatic languages spoken primarily by indigenous Pearic communities in Cambodia and nearby regions, characterized by significant endangerment and distinctive phonological and lexical features.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:30 a.m.