Triple
T26526165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland comprehensive plan |
E670693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-range policy framework |
C17917
|
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: long-range policy framework Context triple: [Portland comprehensive plan, instanceOf, long-range policy framework]
-
A.
national policy framework
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.
-
B.
provincial policy framework
A provincial policy framework is a structured set of guiding principles, objectives, and regulations developed at the provincial level to coordinate and direct public policies, programs, and resource allocation across sectors within that jurisdiction.
-
C.
local and regional planning framework
chosen
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.
-
D.
long-term plan
A long-term plan is a structured, forward-looking strategy that outlines major goals and the sequence of actions needed to achieve them over an extended period of time.
-
E.
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.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:32 a.m.