Triple
T2441847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008–09 NHL season |
E53293
|
entity |
| Predicate | regularSeasonEndDate |
P39355
|
FINISHED |
| Object | 2009-04-12 |
—
|
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: 2009-04-12 | Statement: [2008–09 NHL season, regularSeasonEndDate, 2009-04-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonEndDate Context triple: [2008–09 NHL season, regularSeasonEndDate, 2009-04-12]
-
A.
regularSeasonStart
Indicates the date or point in time when a competition’s regular season officially begins.
-
B.
regularSeasonSuspensionDate
Indicates the date on which a suspension takes effect or applies during the regular season.
-
C.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
D.
featuresRegularSeasonMeetingsPerYear
Indicates that the relationship involves how many regular-season meetings or matchups occur between the entities each year.
-
E.
finalNHLSeason
Indicates the specific NHL season that marks the end or last season of an entity’s participation in the NHL.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
| PDg | Predicate description generation | batch_69abcebe7dd08190b197a2a0e78787e3 |
completed | March 7, 2026, 7:07 a.m. |
Created at: March 6, 2026, 9:43 p.m.