Triple
T8678864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1917–18 NHL season |
E205982
|
entity |
| Predicate | successorSeason |
P43506
|
FINISHED |
| Object | 1918–19 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: 1918–19 NHL season | Statement: [1917–18 NHL season, successorSeason, 1918–19 NHL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorSeason Context triple: [1917–18 NHL season, successorSeason, 1918–19 NHL season]
-
A.
seasonAfter
chosen
Indicates that one season occurs chronologically immediately after another season in a sequence.
-
B.
successorSeries
Indicates that one series directly follows another in sequence, continuing or extending it as its successor.
-
C.
dstSeason
Indicates the specific season during which daylight saving time (DST) is in effect for a given context or location.
-
D.
previousSeason
Indicates that one season directly precedes another in chronological order within the same series or competition.
-
E.
successionYear
Indicates the calendar year in which one entity formally succeeded or took over from another in a given role, position, or status.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.