Triple
T24001241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texcatepec Otomi |
E594253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Oto-Pamean language variety |
C47477
|
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: Oto-Pamean language variety Context triple: [Texcatepec Otomi, instanceOf, Oto-Pamean language variety]
-
A.
Chinookan language variety
A Chinookan language variety is a specific form or dialect of the Chinookan language family traditionally spoken by Indigenous Chinookan peoples of the Pacific Northwest, characterized by its own phonological, grammatical, and lexical features.
-
B.
Kayan language variety
A Kayan language variety is a specific linguistic form or dialect within the Kayan language family, spoken by Kayan communities and characterized by its own phonological, lexical, and grammatical features.
-
C.
Otomi language variety
chosen
An Otomi language variety is a specific regional or social form of the Otomi language, distinguished by its own phonological, lexical, and grammatical features within the broader Otomi linguistic continuum.
-
D.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
E.
Yup'ik language variety
A Yup'ik language variety is a specific regional or social form of the Yup'ik language distinguished by its unique phonological, lexical, and grammatical features within the broader Yup'ik linguistic continuum.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:39 p.m.