Triple
T2446132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riley Cup |
E53597
|
entity |
| Predicate | replacedInSeason |
P24986
|
FINISHED |
| Object | 1996–97 ECHL 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: 1996–97 ECHL season | Statement: [Riley Cup, replacedInSeason, 1996–97 ECHL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedInSeason Context triple: [Riley Cup, replacedInSeason, 1996–97 ECHL season]
-
A.
replacedDuring
chosen
Indicates that one entity took the place of another entity during a specified time period or interval.
-
B.
replacedInYear
Indicates that one entity took the place of or superseded another entity in a specific calendar year.
-
C.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
D.
replacedMLSSeasonBreak
Indicates that one event or schedule change has taken the place of a previously planned MLS season break.
-
E.
originallyPlannedForSeason
Indicates that something (such as an episode, storyline, or content) was initially intended or scheduled to appear in a particular season.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.