Triple
T6561639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uspantek |
E153796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Uspantekan language |
C21586
|
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: Uspantekan language Context triple: [Uspantek, instanceOf, Uspantekan language]
-
A.
Misumalpan language
Misumalpan language is a small family of indigenous languages spoken primarily along the Atlantic coast of Nicaragua and neighboring regions, including Miskito, Sumo (Mayangna), and Matagalpan varieties.
-
B.
Central Tano language
A Central Tano language is a member of the Tano branch of the Niger-Congo language family spoken primarily in Ghana and neighboring regions, characterized by tonal phonology and shared grammatical and lexical features with related Akanic and Guang languages.
-
C.
Zenati language
The Zenati language is a conceptual class representing a branch of Berber languages characterized by shared phonological, morphological, and lexical features that distinguish it from other Afroasiatic language groups.
-
D.
Celebic language
A Celebic language is a member of a subgroup of the Austronesian language family spoken primarily on the island of Sulawesi and nearby smaller islands in Indonesia, characterized by shared phonological and grammatical innovations.
-
E.
Numic language
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.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 1:52 p.m.