Triple
T17391750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Planning Policy Framework |
E422839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planning policy framework |
C23084
|
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: planning policy framework Context triple: [National Planning Policy Framework, instanceOf, planning policy framework]
-
A.
local and regional planning framework
A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
-
B.
national policy framework
chosen
A national policy framework is a structured set of overarching principles, goals, and guidelines that coordinate and align government actions, laws, and programs across sectors to achieve long-term national objectives.
-
C.
planning theory
Planning theory is the body of concepts and frameworks that explains how planning processes are designed, justified, and carried out to guide decision-making and shape future development in societies.
-
D.
municipal policy framework
A municipal policy framework is a structured set of principles, regulations, and procedures that guide a city or local government's decision-making, service delivery, and long-term planning.
-
E.
social policy framework
A social policy framework is a structured set of principles, goals, and guidelines that shapes how a society designs, implements, and evaluates policies to address social needs, inequalities, and welfare.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.