Triple
T2791160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juba Arabic |
E61931
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arabic-based creole |
C10724
|
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: Arabic-based creole Context triple: [Juba Arabic, instanceOf, Arabic-based creole]
-
A.
Bantu-based creole
A Bantu-based creole is a contact language that has developed from the interaction of Bantu languages with one or more other languages, featuring a simplified grammar and mixed vocabulary while retaining a core Bantu structural base.
-
B.
Portuguese-based creole
A Portuguese-based creole is a stable, fully developed language that arose from prolonged contact between Portuguese and one or more other languages, incorporating Portuguese-derived vocabulary within a distinct grammatical and phonological system.
-
C.
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.
-
D.
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.
-
E.
Berber language
Berber language is a branch of the Afroasiatic language family comprising several closely related languages spoken by the indigenous Amazigh peoples of North Africa.
- F. None of above. chosen
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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:58 p.m.