Triple
T25937821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignaciano-Moxo |
E653609
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arawakan language variety |
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 variety Context triple: [Ignaciano-Moxo, instanceOf, Arawakan language variety]
-
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
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.
-
C.
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.
-
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.
regional variety of the Bambara language
A regional variety of the Bambara language is a geographically or socially defined form of Bambara that differs from other varieties in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:39 a.m.