Triple
T12752900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goshute language |
E304779
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Numic language |
C13863
|
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: Central Numic language Context triple: [Goshute language, instanceOf, Central Numic language]
-
A.
Numic language
chosen
A Numic language is any member of a branch of the Uto-Aztecan language family spoken traditionally by Indigenous peoples of the Great Basin and surrounding regions of the western United States, including languages such as Northern Paiute, Shoshoni, and Comanche.
-
B.
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.
-
C.
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.
-
D.
Miwok language
The Miwok language is a group of closely related Native American languages traditionally spoken by the Miwok peoples of central California, known for their rich verb morphology and diverse dialects.
-
E.
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.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:27 p.m.