Triple
T33542695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teke-Ngungwel language |
E859114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Teke language |
C58370
|
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: Teke language Context triple: [Teke-Ngungwel language, instanceOf, Teke language]
-
A.
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.
-
B.
Batanic language
The Batanic language is a subgroup of Austronesian languages spoken primarily in the Batanes Islands of the northern Philippines and nearby areas, characterized by shared phonological and lexical features distinct from neighboring Philippine languages.
-
C.
Katuic language
A Katuic language is a member of a subgroup of the Austroasiatic language family spoken primarily by Katuic ethnic groups in Laos, Vietnam, and neighboring regions, characterized by complex phonologies and rich systems of verbal morphology.
-
D.
Qiangic language
A Qiangic language is a member of a subgroup of Sino-Tibetan languages spoken primarily in Sichuan and nearby regions of China, characterized by complex phonology and diverse morphosyntactic structures.
-
E.
Wintuan language
Wintuan language is a member of a small family of Native American languages historically spoken in the Sacramento Valley of Northern California, known for its complex verb morphology and now largely endangered or extinct.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.