Triple
T26260313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muinane language |
E656828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Colombian indigenous language |
C2456
|
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: Colombian indigenous language Context triple: [Muinane language, instanceOf, Colombian indigenous language]
-
A.
Chibchan language
chosen
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.
-
B.
Mexican indigenous language
A Mexican indigenous language is a native language originating from the diverse Indigenous peoples of Mexico, characterized by unique phonological, grammatical, and cultural features distinct from Spanish and other non-native languages.
-
C.
Andean language
An Andean language is any of the indigenous languages historically spoken in the Andean region of South America, such as Quechua and Aymara, characterized by rich agglutinative morphology and deep cultural significance.
-
D.
Chibchan-speaking people
Chibchan-speaking people are indigenous groups of Central and northern South America who share related Chibchan languages and cultural traditions across regions including present-day Costa Rica, Panama, Colombia, and adjacent areas.
-
E.
Bolivian language
A Bolivian language is any natural language or officially recognized indigenous or colonial tongue that is historically spoken within the geographic and cultural boundaries of Bolivia.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
Created at: April 26, 2026, 9:10 p.m.