Triple
T7872755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Municipal Corporation |
E182777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local self-governing urban body |
C11461
|
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 self-governing urban body Context triple: [City Municipal Corporation, instanceOf, local self-governing urban body]
-
A.
self-governing organization
A self-governing organization is an entity that independently establishes and enforces its own rules, structures, and decision-making processes without external control.
-
B.
municipal organization
chosen
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.
-
C.
autonomous community government
An autonomous community government is a regional governing body with constitutionally recognized self-governing powers to manage political, administrative, and fiscal affairs within its territory under a broader national framework.
-
D.
centrally governed city
A centrally governed city is an urban area whose key administrative, economic, and policy decisions are directed and controlled by a single, central authority rather than by multiple local or decentralized bodies.
-
E.
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.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:56 p.m.