Triple
T6772129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barlavento Creoles |
E155068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Creole dialect cluster |
C5627
|
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: Creole dialect cluster Context triple: [Barlavento Creoles, instanceOf, Creole dialect cluster]
-
A.
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.
-
B.
Atlantic English-lexifier creole
chosen
An Atlantic English-lexifier creole is a creole language that developed around the Atlantic basin with English as its primary lexical source, typically arising from prolonged contact between English speakers and diverse African and other populations in colonial and postcolonial settings.
-
C.
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.
-
D.
French-based creole language
A French-based creole language is a stable, fully developed language that arose from contact between French and one or more other languages, incorporating French-derived vocabulary with distinct grammar and pronunciation.
-
E.
Malay-based creole
A Malay-based creole is a stable contact language that developed from Malay as its primary lexical source, mixed with grammatical and lexical influences from other languages, and used as a native or community language.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:13 p.m.