Triple
T36270101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jebero language |
E892646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Peruvian indigenous language |
C3517
|
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: Peruvian indigenous language Context triple: [Jebero language, instanceOf, Peruvian indigenous language]
-
A.
Andean language
chosen
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.
-
B.
Quechua-speaking people
Quechua-speaking people are Indigenous communities of the Andes and surrounding regions who share a family of Quechuan languages and rich cultural traditions rooted in pre-Columbian civilizations, especially the Inca.
-
C.
Amazonian Kichwa variety
An Amazonian Kichwa variety is a regional form of the Kichwa language spoken by Indigenous communities in the Amazon Basin, characterized by distinct phonological, lexical, and grammatical features shaped by local ecologies and contact with neighboring languages.
-
D.
Nahuan language
A Nahuan language is any member of a group of closely related Uto-Aztecan languages, including Nahuatl and its variants, historically spoken in central Mexico and neighboring regions.
-
E.
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.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.