Triple
T31952597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chedungun |
E815820
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mapuche language variety |
C26439
|
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: Mapuche language variety Context triple: [Chedungun, instanceOf, Mapuche language variety]
-
A.
Tepehua language variety
A Tepehua language variety is a specific regional or community-based form of the Tepehua language, distinguished by its own phonological, lexical, and grammatical features within the broader Totonacan language family.
-
B.
Araucanian language
chosen
The Araucanian language is a family of indigenous languages, primarily represented by Mapudungun, spoken by the Mapuche people of south-central Chile and southwestern Argentina.
-
C.
Ipai-Tipai dialect
The Ipai-Tipai dialect is a variant of the Yuman language continuum spoken by the Kumeyaay (Ipai and Tipai) people of southern California and northern Baja California, characterized by closely related but distinct regional speech forms.
-
D.
Huave language variety
A Huave language variety is a specific regional or community-based form of the Huave language, distinguished by its own phonological, lexical, and grammatical features within the broader Huave linguistic continuum.
-
E.
Cuicatec language variety
A Cuicatec language variety is a specific regional or social form of the Cuicatec language, distinguished by its unique phonological, lexical, and grammatical features within the broader Cuicatec linguistic continuum.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:07 a.m.