Triple
T13983678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willamette Greenway Plan |
E336378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public policy document |
C34448
|
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: public policy document Context triple: [Willamette Greenway Plan, instanceOf, public policy document]
-
A.
public policy book
A public policy book is a written work that analyzes, explains, or critiques government policies and policymaking processes, often offering frameworks, evidence, and recommendations for addressing societal issues.
-
B.
public policy office
A public policy office is an organizational unit within a government or institution responsible for researching, developing, analyzing, and coordinating policies to address public issues and guide decision-making.
-
C.
public policy doctrine
A public policy doctrine is a legal principle that allows courts or governments to limit, invalidate, or shape actions, contracts, or decisions that conflict with the broader interests, values, or welfare of society.
-
D.
public policy domain
The public policy domain encompasses the processes, institutions, and frameworks through which governments and stakeholders identify societal issues, design and implement policy solutions, and evaluate their impacts on the public.
-
E.
public policy stance
A public policy stance is a defined position or viewpoint held by an individual or organization regarding how government should address specific societal issues through laws, regulations, and programs.
- F. None of above. chosen
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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.