Triple
T8758084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pemon language |
E208122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cariban language |
C25027
|
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: Cariban language Context triple: [Pemon language, instanceOf, Cariban language]
-
A.
Arawakan language
An Arawakan language is any member of a large family of indigenous languages of South America and the Caribbean, historically spoken across a vast area from the Amazon Basin to the Antilles.
-
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.
Chibchan language
A Chibchan language is a member of a family of indigenous languages spoken primarily in Central America and northern South America, characterized by shared grammatical and phonological features reflecting a common ancestral origin.
-
D.
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.
-
E.
Caribbean creole language
A Caribbean creole language is a stable, fully developed natural language that emerged in the Caribbean from the contact and blending of European colonial languages with African, Indigenous, and other linguistic influences.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:40 p.m.