Triple
T2542564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhaca polity |
E57817
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Xhosa-speaking polity |
C7545
|
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: Xhosa-speaking polity Context triple: [Bhaca polity, instanceOf, Xhosa-speaking polity]
-
A.
Shona-speaking polity
A Shona-speaking polity is a socio-political entity historically or contemporarily organized around communities whose primary language and cultural identity are Shona, typically located in present-day Zimbabwe and surrounding regions.
-
B.
Bantu people
chosen
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.
-
C.
language of South Africa
A language of South Africa is a system of spoken and/or written communication, such as Zulu, Xhosa, Afrikaans, or others, used by communities within South Africa for everyday interaction, cultural expression, and official purposes.
-
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.
Bantu-based creole
A Bantu-based creole is a contact language that has developed from the interaction of Bantu languages with one or more other languages, featuring a simplified grammar and mixed vocabulary while retaining a core Bantu structural base.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:47 p.m.