Triple
T22524859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five-Year Plans of India |
E556872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government development plan |
C37305
|
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: government development plan Context triple: [Five-Year Plans of India, instanceOf, government development plan]
-
A.
political plan
A political plan is a structured strategy outlining specific policies, actions, and timelines that a political actor intends to pursue to achieve defined governance or electoral objectives.
-
B.
planning commission
A planning commission is a governmental or advisory body responsible for reviewing, guiding, and making recommendations on land use, development proposals, and long-term community planning policies.
-
C.
citywide planning initiative
A citywide planning initiative is a coordinated, long-term effort by municipal stakeholders to guide land use, infrastructure, services, and development policies across an entire city to achieve shared social, economic, and environmental goals.
-
D.
development policy
chosen
Development policy is a set of strategic guidelines and interventions designed by governments or organizations to promote sustainable economic growth, social welfare, and institutional improvement within a country or region.
-
E.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:51 p.m.