Triple
T21558491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mojeño |
E531953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arawakan language group |
C14586
|
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: Arawakan language group Context triple: [Mojeño, instanceOf, Arawakan language group]
-
A.
Arawakan language
chosen
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.
creole language group
A creole language group is a collection of fully developed natural languages that have evolved from the contact, mixing, and nativization of multiple parent languages, typically emerging in multilingual and colonial 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.
Cariban language
A Cariban language is a member of the Cariban family of indigenous languages spoken primarily in northern South America, known for their complex verb morphology and diverse phonological systems.
-
E.
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.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:29 p.m.