Triple
T4152739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miskito |
E89944
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Misumalpan language |
C15041
|
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: Misumalpan language Context triple: [Miskito, instanceOf, Misumalpan language]
-
A.
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.
-
B.
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.
-
C.
Munda language
The Munda language is a member of the Austroasiatic language family spoken primarily by indigenous Munda communities in eastern and central India, characterized by agglutinative morphology and distinct phonological features.
-
D.
Great Andamanese language
The Great Andamanese language is an endangered mixed language spoken by the indigenous Great Andamanese people of the Andaman Islands, combining elements from several original Andamanese languages with influences from Hindi and other contact languages.
-
E.
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.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:44 p.m.