Triple
T8409134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada Pension Plan |
E198577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public pension program |
C7279
|
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 pension program Context triple: [Canada Pension Plan, instanceOf, public pension program]
-
A.
pension plan
chosen
A pension plan is a long-term savings and investment arrangement, typically sponsored by an employer or government, that provides individuals with regular income payments after retirement based on contributions and plan rules.
-
B.
employee benefit plan
An employee benefit plan is an organized program established by an employer to provide workers with non-wage compensation such as health insurance, retirement savings, paid leave, and other benefits.
-
C.
multiemployer benefit plan
A multiemployer benefit plan is a collectively bargained employee benefit arrangement maintained by two or more unrelated employers, typically within the same industry, and administered by a joint board of trustees representing both employers and labor unions.
-
D.
public employment program
A public employment program is a government-initiated scheme that directly creates temporary or permanent jobs, typically in public works or community services, to reduce unemployment and support income for targeted populations.
-
E.
health and welfare benefit plan
A health and welfare benefit plan is an employer- or organization-sponsored program that provides employees and their dependents with non-retirement benefits such as medical, dental, vision, disability, and life insurance coverage.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:05 p.m.