Triple
T35509494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gbagyi language |
E1026245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Nigerian language |
C34403
|
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: Central Nigerian language Context triple: [Gbagyi language, instanceOf, Central Nigerian language]
-
A.
Igbo-speaking region
The Igbo-speaking region is a culturally and linguistically unified area in southeastern Nigeria where the Igbo language predominates and shared social, economic, and traditional practices define community life.
-
B.
regional variety of the Nupe language
A regional variety of the Nupe language is a geographically or socially defined form of Nupe that exhibits distinct phonological, lexical, or grammatical features while remaining mutually intelligible with other Nupe varieties.
-
C.
Volta–Niger language
chosen
A Volta–Niger language is a member of a proposed branch of the Niger–Congo language family spoken primarily in southern Nigeria and neighboring regions, characterized by significant lexical and grammatical diversity among its constituent languages.
-
D.
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.
-
E.
Central African Banda language
Central African Banda language is a group of closely related Ubangian languages spoken primarily by the Banda people in the Central African Republic and neighboring regions.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.