Triple
T22001035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WE Charity controversy |
E543325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian political controversy |
C9175
|
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: Canadian political controversy Context triple: [WE Charity controversy, instanceOf, Canadian political controversy]
-
A.
Canadian federal government policy
Canadian federal government policy is the set of laws, regulations, programs, and strategic decisions enacted by the national government to address public issues and guide the country’s social, economic, environmental, and international directions.
-
B.
public policy controversy
chosen
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
-
C.
political issue
A political issue is a topic or problem related to governance, public policy, or societal values that generates debate and requires collective decision-making or action.
-
D.
Canadian federal bill
A Canadian federal bill is a proposed law presented to the Parliament of Canada for debate, amendment, and approval before it can receive Royal Assent and become part of federal legislation.
-
E.
British political crisis
A British political crisis is a period of acute instability in the United Kingdom’s governance marked by intense conflict among political actors, breakdowns in normal decision-making processes, and heightened uncertainty about leadership, policy direction, or constitutional arrangements.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:20 p.m.