Triple
T24831687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochester City Council Vice President |
E621356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | city council leadership role |
C45038
|
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: city council leadership role Context triple: [Rochester City Council Vice President, instanceOf, city council leadership role]
-
A.
municipal political organization leadership
Municipal political organization leadership encompasses the individuals and structures responsible for guiding, coordinating, and representing a city or town’s political party activities, strategies, and community engagement at the local level.
-
B.
civic leader
A civic leader is an individual who actively guides, organizes, and advocates within a community or public sphere to address collective needs, shape policy, and promote the common good.
-
C.
municipal government position
A municipal government position is a role within a city or local government responsible for administering public services, implementing local policies, and managing community resources and regulations.
-
D.
local government role
chosen
A local government role is a position within municipal or regional authorities responsible for managing community services, implementing local policies, and representing residents’ interests in public decision-making.
-
E.
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.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:15 a.m.