Triple
T14786277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebat Bet Gurage |
E347533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Ethiopian language |
C26417
|
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: Southern Ethiopian language Context triple: [Sebat Bet Gurage, instanceOf, Southern Ethiopian language]
-
A.
South Ethiopic Semitic language
chosen
A South Ethiopic Semitic language is a member of the Semitic branch of the Afroasiatic family spoken in southern Ethiopia, characterized by shared phonological, morphological, and syntactic features distinct to this regional subgroup.
-
B.
Southern Nilotic language
A Southern Nilotic language is a member of the Nilotic branch of the Nilo-Saharan language family spoken primarily in parts of Kenya, Tanzania, and Uganda, characterized by complex tonal systems and rich noun morphology.
-
C.
Cushitic language
A Cushitic language is a member of a branch of the Afroasiatic language family spoken primarily in the Horn of Africa and parts of East Africa, characterized by shared grammatical and phonological features distinct from other Afroasiatic branches.
-
D.
Songhay language
Songhay language is a group of closely related Nilo-Saharan languages spoken primarily along the Niger River in Mali, Niger, and neighboring West African countries.
-
E.
Central Sudanic language
A Central Sudanic language is a member of a branch of the Nilo-Saharan language family spoken primarily in central Africa, characterized by diverse phonological systems and complex noun class or gender distinctions.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.