Triple
T8618342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland City Council committees |
E204098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government working group |
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 working group Context triple: [Portland City Council committees, instanceOf, local government working group]
-
A.
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.
-
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.
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.
-
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 organization
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.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:26 p.m.