Triple
T8409156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada Pension Plan |
E198577
|
entity |
| Predicate | contributionBasis |
P32723
|
FINISHED |
| Object | pensionable earnings |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: pensionable earnings | Statement: [Canada Pension Plan, contributionBasis, pensionable earnings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributionBasis Context triple: [Canada Pension Plan, contributionBasis, pensionable earnings]
-
A.
contributionBase
chosen
Indicates the foundational amount, value, or resource on which a contribution, payment, or benefit is calculated or determined.
-
B.
calculationBasis
Indicates the rule, method, or reference standard used as the foundation for performing a calculation in the relationship.
-
C.
usedAsBasisFor
Indicates that one entity serves as the foundation, reference, or starting point upon which another entity is developed, derived, justified, or constructed.
-
D.
assignmentBasis
Indicates the criterion or rationale on which an assignment or allocation is determined.
-
E.
exclusionBasis
Indicates the reason or criterion used to exclude an entity from a set, process, or consideration.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69cb8317045c8190b69cc99854b633be |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.