Triple
T38613136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biafada |
E934533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | West Atlantic language |
C20551
|
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: West Atlantic language Context triple: [Biafada, instanceOf, West Atlantic language]
-
A.
Atlantic language
chosen
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.
-
B.
Atlantic English-lexifier creole
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.
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.
-
D.
Atlantic-Congo language
An Atlantic-Congo language is a member of a major branch of the Niger-Congo language family, encompassing a vast and diverse group of languages spoken primarily in sub-Saharan Africa.
-
E.
creole language variety
A creole language variety is a fully developed, stable natural language that has evolved from the mixing and nativization of multiple languages, typically emerging in contexts of prolonged contact and serving as a primary means of communication for a community.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.