Triple
T6334216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarawan Bantu |
E142451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bantu-related language group |
C3817
|
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: Bantu-related language group Context triple: [Jarawan Bantu, instanceOf, Bantu-related language group]
-
A.
Bantu language
chosen
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.
-
B.
African language
An African language is any of the diverse indigenous or historically rooted languages spoken across the African continent, encompassing numerous families such as Niger-Congo, Afroasiatic, Nilo-Saharan, and Khoisan.
-
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.
branch of Nilo-Saharan languages
A branch of Nilo-Saharan languages is a subgroup within the proposed Nilo-Saharan language family, consisting of related languages that share common historical origins and linguistic features.
-
E.
Bantu people
The Bantu people are a large, diverse group of African ethnic communities linked by related Bantu languages and shared historical origins in central and western Africa, whose migrations significantly shaped the continent’s cultural, linguistic, and demographic landscape.
- 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:30 p.m.