Triple
T11218720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipil (Nawat) |
E265504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nahuan language |
C29384
|
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: Nahuan language Context triple: [Pipil (Nawat), instanceOf, Nahuan language]
-
A.
Araucanian language
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.
-
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.
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.
-
D.
Quechuan language
A Quechuan language is any member of a family of indigenous languages of the Andes, primarily spoken in Peru, Bolivia, Ecuador, Colombia, and Argentina, that share common grammatical structures and vocabulary derived from a Proto-Quechuan ancestor.
-
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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:30 p.m.