Triple
T8387567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazatec languages |
E197857
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Otomanguean language |
C12029
|
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: Otomanguean language Context triple: [Mazatec languages, instanceOf, Otomanguean language]
-
A.
Oto-Manguean language
chosen
An Oto-Manguean language is a member of a large, diverse family of indigenous Mesoamerican languages, primarily spoken in Mexico, characterized by complex tonal systems and significant grammatical and phonological variation.
-
B.
Uto-Aztecan language
A Uto-Aztecan language is a member of a Native American language family spoken from the western United States through northern and central Mexico, sharing common ancestral linguistic features despite diverse cultures and regions.
-
C.
Bantoid languages
Bantoid languages are a branch of the Benue–Congo family within the Niger–Congo language phylum, comprising Bantu and closely related non-Bantu languages spoken primarily in Central and West Africa.
-
D.
Hokan language
Hokan language is a proposed but controversial grouping of several Native American language families and isolates of western North America, hypothesized to share a distant common ancestor.
-
E.
Ubangian language
A Ubangian language is a member of a proposed group of Central African languages, primarily spoken in the Central African Republic and neighboring countries, that share common phonological and grammatical features and are often considered a branch of the Niger-Congo family.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:03 p.m.