Triple
T32105402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teutila Cuicatec |
E819967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cuicatec language variety |
C57638
|
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: Cuicatec language variety Context triple: [Teutila Cuicatec, instanceOf, Cuicatec language variety]
-
A.
Mazatec language variety
A Mazatec language variety is a specific regional or social form of the Mazatec language, characterized by distinct phonological, lexical, and grammatical features within the broader Mazatecan linguistic continuum.
-
B.
Matlatzinca language variety
A Matlatzinca language variety is a specific regional or social form of the Matlatzinca language, distinguished by its unique phonological, lexical, and grammatical features within the broader Matlatzinca linguistic continuum.
-
C.
Kaqchikel language variety
The Kaqchikel language variety is a Mayan language spoken primarily in the central highlands of Guatemala, characterized by its agglutinative morphology, ergative-absolutive alignment, and rich system of aspect and status markers.
-
D.
Mixtec language variety
A Mixtec language variety is a specific regional or community-based form of the Mixtec language, characterized by its own distinct phonological, lexical, and grammatical features within the broader Mixtecan language continuum.
-
E.
Mazahua language variety
A Mazahua language variety is a specific regional or social form of the Mazahua language, characterized by distinct phonological, lexical, and grammatical features within the broader Mazahua linguistic continuum.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:27 a.m.