Triple
T18283218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincolnshire Wolds Countryside Service |
E437914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government service |
C40093
|
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 service Context triple: [Lincolnshire Wolds Countryside Service, instanceOf, local government service]
-
A.
regional government service
A regional government service is an administrative entity that delivers public programs, resources, and regulatory functions within a specific geographic area under the authority of a higher-level government.
-
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.
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.
-
D.
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.
-
E.
municipal administration
Municipal administration is the organizational structure and processes through which a local government manages public services, implements policies, and oversees the day-to-day operations of a municipality.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:35 a.m.