Triple
T25379482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griqua polity around Kimberley |
E631343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Griqua-ruled territory |
C21391
|
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: Griqua-ruled territory Context triple: [Griqua polity around Kimberley, instanceOf, Griqua-ruled territory]
-
A.
South African territory
A South African territory is a defined geographic area under the sovereignty or administration of South Africa, subject to its legal, political, and jurisdictional authority.
-
B.
historical Boer republic
A historical Boer republic is a 19th- to early 20th-century self-governing state established in southern Africa by Dutch-speaking settlers (Boers) seeking political independence from British colonial rule.
-
C.
former territory in southern Africa
chosen
A former territory in southern Africa is a historically defined geographic and political region within the southern part of the African continent that once existed as a distinct colonial, mandated, or administrative unit but no longer holds that status.
-
D.
Bantustan
A Bantustan was a territory set aside for black inhabitants of South Africa and South West Africa (Namibia) during apartheid, intended to serve as a pseudo-independent homeland that reinforced racial segregation and white minority rule.
-
E.
Bantu state
A Bantu state is a political entity historically or contemporarily governed by Bantu-speaking peoples, typically characterized by centralized authority, kinship-based social organization, and economies rooted in agriculture, herding, and regional trade.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:46 p.m.