Triple
T37236271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zing Mumuye |
E923583
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Mumuye language |
C64971
|
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 Mumuye language Context triple: [Zing Mumuye, instanceOf, variety of Mumuye language]
-
A.
variety of the Uma language
A variety of the Uma language is a distinct regional or social form of Uma characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
B.
variety of Mwaghavul language
A variety of the Mwaghavul language is a distinct regional or social form of Mwaghavul characterized by systematic differences in pronunciation, vocabulary, and/or grammar within the broader Mwaghavul-speaking community.
-
C.
variety of the Myene language
A variety of the Myene language is a distinct regional or social form of Myene characterized by systematic differences in pronunciation, vocabulary, and/or grammar while remaining mutually intelligible with other Myene forms.
-
D.
Moru language variety
A Moru language variety is a specific regional or social form of the Moru language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Moru linguistic continuum.
-
E.
Mari language variety
A Mari language variety is a specific form or dialect of the Mari language, distinguished by its unique phonological, grammatical, and lexical features used by a particular Mari-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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.