Triple
T23976855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipal council of Medemblik |
E604393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | elected local government body |
C11461
|
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: elected local government body Context triple: [municipal council of Medemblik, instanceOf, elected local government body]
-
A.
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.
-
B.
regional electoral body
A regional electoral body is an organization responsible for administering, supervising, and ensuring the integrity of elections within a specific subnational geographic area.
-
C.
municipal organization
chosen
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.
system of local government
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.
-
E.
municipal board
A municipal board is a local governing body composed of appointed or elected members responsible for making decisions, setting policies, and overseeing specific functions or services within a municipality.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:26 p.m.