Triple
T9694380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapudungun |
E234610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Araucanian language |
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: Araucanian language Context triple: [Mapudungun, instanceOf, Araucanian language]
-
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.
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.
-
C.
Cariban language
A Cariban language is a member of the Cariban family of indigenous languages spoken primarily in northern South America, known for their complex verb morphology and diverse phonological systems.
-
D.
Miwok language
The Miwok language is a group of closely related Native American languages traditionally spoken by the Miwok peoples of central California, known for their rich verb morphology and diverse dialects.
-
E.
Cordilleran language
A Cordilleran language is a member of a proposed subgroup of the Austronesian language family spoken in the Cordillera mountain region of northern Luzon in the Philippines, characterized by shared phonological, lexical, and grammatical features distinct from neighboring language groups.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:17 p.m.