Triple
T19318425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cincinnati Charter Committee leadership |
E483157
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal political organization leadership |
C41913
|
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: municipal political organization leadership Context triple: [Cincinnati Charter Committee leadership, instanceOf, municipal political organization leadership]
-
A.
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.
-
B.
municipal administration
Municipal administration is the organizational structure and processes through which a local government manages public services, implements policies, and oversees the day-to-day operations of a municipality.
-
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.
municipal government officeholders
Individuals elected or appointed to positions of authority within a city or local government, responsible for creating, implementing, and overseeing municipal policies, services, and regulations.
-
E.
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.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:32 p.m.