Triple
T11938992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jicarilla language |
E284125
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Apachean language |
C10973
|
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: Apachean language Context triple: [Jicarilla language, instanceOf, Apachean language]
-
A.
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.
-
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.
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.
-
D.
Southern Athabaskan language
chosen
A Southern Athabaskan language is a member of the Athabaskan branch of the Na-Dené language family spoken primarily in the Southwestern United States and northern Mexico, characterized by complex verb morphology and tonal or pitch-accent features.
-
E.
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.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:45 p.m.