Triple
T21755603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budget and Fiscal Management Committee |
E537030
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | King County Council 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: King County Council committee Context triple: [Budget and Fiscal Management Committee, instanceOf, King County Council committee]
-
A.
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.
-
B.
city commission
A city commission is a governing body, typically composed of elected or appointed officials, responsible for making policy decisions, overseeing municipal services, and guiding the development and administration of a city.
-
C.
county council
A county council is a local governing body elected to make decisions, set policies, and oversee public services within a county’s jurisdiction.
-
D.
committee of the New York City Council
A committee of the New York City Council is a specialized subgroup of council members responsible for reviewing, holding hearings on, and making recommendations regarding legislation and oversight within a specific policy area affecting the city.
-
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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:50 p.m.