Triple
T25976912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clyde Muirshiel Park Authority |
E645966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government joint committee |
C50399
|
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 joint committee Context triple: [Clyde Muirshiel Park Authority, instanceOf, local government joint committee]
-
A.
municipal government committee
A municipal government committee is a formally organized group within a local government tasked with studying specific issues, advising the city or town council, and sometimes making decisions or recommendations on policies, services, and regulations affecting the community.
-
B.
county government committee
A county government committee is a formally organized group within county administration tasked with studying specific issues, advising elected officials, and sometimes making decisions or recommendations on local policies, budgets, and services.
-
C.
local government association
A local government association is an organization that represents and supports the collective interests, coordination, and capacity-building of local authorities within a specific region or country.
-
D.
municipal advisory committee
A municipal advisory committee is a formally appointed group of community members that provides recommendations and expert input to local government officials on specific policy areas, projects, or issues.
-
E.
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.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:52 a.m.