Triple
T6297589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vhembe District Municipality |
E141169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Municipality of South Africa |
C20290
|
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: Municipality of South Africa Context triple: [Vhembe District Municipality, instanceOf, Municipality of South Africa]
-
A.
province of South Africa
A province of South Africa is a primary administrative division of the country, each with its own government structures, geographic boundaries, and socio-economic characteristics under the national constitution.
-
B.
country in Southern Africa
A country in Southern Africa is a sovereign state located in the southern region of the African continent, typically characterized by shared geographic proximity, regional economic and political ties, and often diverse cultural and linguistic communities.
-
C.
former province of South Africa
A former province of South Africa is an administrative territorial division that existed under earlier constitutional arrangements of the country but has since been restructured, renamed, or dissolved in subsequent political reforms.
-
D.
province of Zimbabwe
A province of Zimbabwe is a primary administrative division of the country, governed by provincial authorities and comprising multiple districts, towns, and rural areas.
-
E.
municipality in Argentina
A municipality in Argentina is a local administrative division governed by an elected council and mayor, responsible for providing public services and managing community affairs within its defined territory.
- F. None of above. chosen
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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:27 p.m.