Triple
T4464150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka Metropolis plan advocacy |
E98333
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government reform movement |
C2079
|
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 movement Context triple: [Osaka Metropolis plan advocacy, instanceOf, local government reform movement]
-
A.
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.
-
B.
political reform process
The political reform process is the sequence of activities through which political institutions, laws, and practices are evaluated, negotiated, and altered to address societal demands and improve governance.
-
C.
political reform
chosen
Political reform is the deliberate process of changing laws, institutions, or governance practices to improve political fairness, accountability, and effectiveness within a society.
-
D.
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.
-
E.
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.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:34 p.m.