Triple
T11721155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Cahuilla |
E278632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cahuilla language variety |
C30429
|
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: Cahuilla language variety Context triple: [Mountain Cahuilla, instanceOf, Cahuilla language variety]
-
A.
Yavapai language variety
A Yavapai language variety is a specific form or dialect of the Yavapai language, distinguished by unique phonological, lexical, or grammatical features used by a particular Yavapai-speaking community.
-
B.
Amuzgo language variety
An Amuzgo language variety is a specific regional or social form of the Amuzgo language, distinguished by its unique phonological, lexical, and grammatical features within the broader Amuzgo linguistic continuum.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.