Triple
T31958311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungerford Finance and General Purposes Committee |
E815966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government committee |
C7575
|
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 committee Context triple: [Hungerford Finance and General Purposes Committee, instanceOf, local government committee]
-
A.
local government joint committee
A local government joint committee is a collaborative body formed by two or more local authorities to exercise specific functions or deliver shared services on their behalf.
-
B.
municipal government committee
chosen
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.
-
C.
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.
-
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.
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.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:08 a.m.