Triple
T25601935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003–04 NHL season |
E641809
|
entity |
| Predicate | salaryCapInEffect |
P2676
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [2003–04 NHL season, salaryCapInEffect, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salaryCapInEffect Context triple: [2003–04 NHL season, salaryCapInEffect, no]
-
A.
usesSalaryCap
chosen
Indicates that an entity applies or operates under a salary cap constraint when managing compensation or payroll.
-
B.
salaryCapUpperLimitUSD
Indicates the maximum allowable salary amount, expressed in U.S. dollars, that an entity (such as a person, team, or organization) is permitted to pay or receive under a defined cap or budget constraint.
-
C.
introducedSalaryCapSeason
Indicates the season during which a salary cap was first implemented or introduced.
-
D.
averagePlayerSalary
Indicates the typical or mean salary earned by players within a specified group or context.
-
E.
subjectToAnnualCap
Indicates that the related amount, usage, or activity is limited by a maximum allowable value that applies on an annual basis.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a7d7d881909014fdf3746f981b |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:31 p.m.