Triple
T3669973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wipukpa dialect |
E77854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yavapai language variety |
C12930
|
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: Yavapai language variety Context triple: [Wipukpa dialect, instanceOf, Yavapai language variety]
-
A.
Southern Athabaskan language
A Southern Athabaskan language is a member of the Athabaskan branch of the Na-Dené language family spoken primarily in the Southwestern United States and northern Mexico, characterized by complex verb morphology and tonal or pitch-accent features.
-
B.
Uto-Aztecan language
A Uto-Aztecan language is a member of a Native American language family spoken from the western United States through northern and central Mexico, sharing common ancestral linguistic features despite diverse cultures and regions.
-
C.
Central Tano language
A Central Tano language is a member of the Tano branch of the Niger-Congo language family spoken primarily in Ghana and neighboring regions, characterized by tonal phonology and shared grammatical and lexical features with related Akanic and Guang languages.
-
D.
Chibchan language
A Chibchan language is a member of a family of indigenous languages spoken primarily in Central America and northern South America, characterized by shared grammatical and phonological features reflecting a common ancestral origin.
-
E.
Banda languages
Banda languages are a group of closely related Ubangian languages spoken primarily in the Central African Republic and neighboring regions, characterized by shared phonological and grammatical 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:25 p.m.