Triple
T35688019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mpumalanga local government sphere |
E1031204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government sphere |
C65458
|
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: local government sphere Context triple: [Mpumalanga local government sphere, instanceOf, local government sphere]
-
A.
local government politics
Local government politics encompasses the processes, power dynamics, and decision-making activities through which local officials, institutions, and community stakeholders shape policies and allocate resources within municipalities or regions.
-
B.
local government role
A local government role is a position within municipal or regional authorities responsible for managing community services, implementing local policies, and representing residents’ interests in public decision-making.
-
C.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
D.
local council
A local council is a governing body elected or appointed to make decisions, set policies, and manage public services for a specific municipality or local area.
-
E.
local government service
A local government service is a public function or resource provided by municipal or regional authorities to meet community needs such as safety, infrastructure, health, and social support.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.