Triple
T23741342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mbula-Bwazza |
E586680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jarawan Bantu language |
C20849
|
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: Jarawan Bantu language Context triple: [Mbula-Bwazza, instanceOf, Jarawan Bantu language]
-
A.
Ubangian language
A Ubangian language is a member of a proposed group of Central African languages, primarily spoken in the Central African Republic and neighboring countries, that share common phonological and grammatical features and are often considered a branch of the Niger-Congo family.
-
B.
Sabaki language
Sabaki language is a conceptual class representing a subgroup of closely related Bantu languages spoken along the East African coast, characterized by shared phonological, lexical, and grammatical features.
-
C.
Nobiin language
Nobiin language is a Northern Nubian language of the Nilo-Saharan family spoken primarily along the Nile in southern Egypt and northern Sudan, notable for its rich oral tradition and historical significance in Nubian culture.
-
D.
Batanic language
The Batanic language is a subgroup of Austronesian languages spoken primarily in the Batanes Islands of the northern Philippines and nearby areas, characterized by shared phonological and lexical features distinct from neighboring Philippine languages.
-
E.
Bantoid languages
chosen
Bantoid languages are a branch of the Benue–Congo family within the Niger–Congo language phylum, comprising Bantu and closely related non-Bantu languages spoken primarily in Central and West Africa.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:11 p.m.