Triple
T18434126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Columbia Treaty Process |
E450348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public policy process |
C29106
|
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 process Context triple: [British Columbia Treaty Process, instanceOf, public policy process]
-
A.
public policy mechanism
chosen
A public policy mechanism is a structured tool, process, or instrument used by governments or public institutions to influence behavior, allocate resources, or achieve specific societal outcomes.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
public policy document
A public policy document is an official written statement issued by a government or public institution that outlines decisions, rules, or strategies intended to address societal issues and guide future actions.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:28 a.m.