Triple
T6548207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saramaccan language |
E151063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Atlantic creole |
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: Atlantic creole Context triple: [Saramaccan language, instanceOf, Atlantic creole]
-
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.
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.
-
C.
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.
-
D.
creole people
Creole people are ethnically and culturally distinct groups that emerged from the blending of European, African, Indigenous, and sometimes Asian ancestries, often in colonial or postcolonial societies, with their own unique languages, traditions, and identities.
-
E.
Atlantic language
Atlantic language is a member of a branch of the Niger-Congo language family spoken primarily along the Atlantic coast of West Africa, characterized by diverse phonological systems and noun class structures.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:51 p.m.