Triple
T28748725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YMPE |
E731453
|
entity |
| Predicate | upperLimitFor |
P36360
|
FINISHED |
| Object | CPP contributory 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: CPP contributory earnings | Statement: [YMPE, upperLimitFor, CPP contributory earnings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperLimitFor Context triple: [YMPE, upperLimitFor, CPP contributory earnings]
-
A.
upperLimit
chosen
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
B.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
C.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
D.
innerLimit
Indicates a boundary or maximum value that applies within a specified internal or constrained context of something.
-
E.
upperBoundaryType
Indicates the kind or classification of the upper boundary that limits or caps a given range, interval, or extent.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:06 a.m.