Triple
T36969500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Gumuz dialect |
E914521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Gumuz language |
C29231
|
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: regional variety of Gumuz language Context triple: [Southern Gumuz dialect, instanceOf, regional variety of Gumuz language]
-
A.
Gumuz language variety
chosen
A Gumuz language variety is a specific form or dialect of the Gumuz language, distinguished by its unique phonological, lexical, or grammatical features within the broader Gumuz linguistic continuum.
-
B.
Gurage language variety
A Gurage language variety is a specific form of speech within the Gurage branch of South Ethiosemitic languages, distinguished by its unique phonological, lexical, and grammatical features used by particular Gurage communities in Ethiopia.
-
C.
Gumuz language
The Gumuz language is a Nilo-Saharan language spoken primarily by the Gumuz people in western Ethiopia and adjacent regions of Sudan.
-
D.
regional variety of Ghomalaʼ language
A regional variety of the Ghomalaʼ language is a geographically or socially distinct form of Ghomalaʼ characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Ghomalaʼ varieties.
-
E.
regional variety of Lezgian
A regional variety of Lezgian is a geographically distinct form of the Lezgian language characterized by unique phonological, lexical, and grammatical features shared by speakers in a particular area.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.