Triple
T22327723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proposition E (San Francisco, 1999) |
E551943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government reform measure |
C21172
|
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 reform measure Context triple: [Proposition E (San Francisco, 1999), instanceOf, local government reform measure]
-
A.
local government reform
chosen
Local government reform is the process of restructuring and improving local administrative, political, and fiscal systems to enhance efficiency, accountability, and responsiveness to community needs.
-
B.
local government act
A local government act is a legislative framework that defines the powers, responsibilities, structure, and operation of local authorities within a specific jurisdiction.
-
C.
system of local government
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
D.
local government politics
Local government politics encompasses the processes, power dynamics, and decision-making activities through which local officials, institutions, and community stakeholders shape policies and allocate resources within municipalities or regions.
-
E.
local government role
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.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.