Triple
T23348539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mungo |
E591937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Duala language |
C47547
|
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: variety of the Duala language Context triple: [Mungo, instanceOf, variety of the Duala language]
-
A.
variety of the Dinka language
A variety of the Dinka language is a specific regional or social form of Dinka distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Dinka varieties.
-
B.
Fula language variety
A Fula language variety is a specific regional or social form of the Fula (Fulfulde/Pulaar/Pular) language distinguished by its phonological, lexical, and grammatical features within the broader Fula continuum.
-
C.
variety of the Nuer language
A variety of the Nuer language is a distinct regional or social form of Nuer characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other Nuer forms.
-
D.
Songhay language variety
A Songhay language variety is a specific regional or social form of the Songhay language continuum, distinguished by its unique phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Songhay varieties.
-
E.
Nubian language variety
A Nubian language variety is a specific form or dialect of the Nubian language continuum, distinguished by its unique phonological, grammatical, and lexical features used by a particular Nubian-speaking community.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:19 p.m.