Triple
T6835482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unigov |
E157438
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | form of local government |
C8884
|
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: form of local government Context triple: [Unigov, instanceOf, form of local government]
-
A.
system of local government
chosen
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
B.
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.
-
C.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
D.
autonomous community government
An autonomous community government is a regional governing body with constitutionally recognized self-governing powers to manage political, administrative, and fiscal affairs within its territory under a broader national framework.
-
E.
municipality
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:19 p.m.