Triple
T24478339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guang languages |
E617293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Niger–Congo language subgroup |
C38316
|
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: Niger–Congo language subgroup Context triple: [Guang languages, instanceOf, Niger–Congo language subgroup]
-
A.
Niger-Congo language family
chosen
The Niger-Congo language family is a large and diverse group of languages spoken primarily in sub-Saharan Africa, characterized by features such as noun class systems and tonal distinctions.
-
B.
Atlantic-Congo language
An Atlantic-Congo language is a member of a major branch of the Niger-Congo language family, encompassing a vast and diverse group of languages spoken primarily in sub-Saharan Africa.
-
C.
Nilo-Saharan language
A Nilo-Saharan language is a member of a proposed but controversial language family spoken primarily along the Nile and across parts of central and eastern Africa, characterized by significant internal diversity and debated genetic relationships.
-
D.
Bantu language
A Bantu language is a member of a large branch of the Niger-Congo language family, spoken primarily in central, eastern, and southern Africa, characterized by noun class systems and agglutinative morphology.
-
E.
Volta–Niger language
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.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.