Triple
T1056310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL on TNT |
E22802
|
entity |
| Predicate | contractEndSeason |
P22977
|
FINISHED |
| Object | 2027–28 NHL season |
—
|
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: 2027–28 NHL season | Statement: [NHL on TNT, contractEndSeason, 2027–28 NHL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractEndSeason Context triple: [NHL on TNT, contractEndSeason, 2027–28 NHL season]
-
A.
contractStartSeason
Indicates the season during which a contract between entities begins or becomes effective.
-
B.
endSeason
Indicates the action or event of bringing a particular season, series, or period to a close.
-
C.
typicalEndSeason
Indicates the season in which something (such as an activity, event, or condition) usually or characteristically comes to an end.
-
D.
seasonCulminatesIn
Indicates that a particular season reaches its peak, conclusion, or defining outcome in the specified event or state.
-
E.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
- F. None of above. chosen
Provenance (4 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d9102c819090af78cae50f0ff2 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:42 p.m.