Triple
T7830875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Ice Hockey Superleague |
E181362
|
entity |
| Predicate | hadPlayoffFinalsWeekend |
P2675
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [British Ice Hockey Superleague, hadPlayoffFinalsWeekend, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPlayoffFinalsWeekend Context triple: [British Ice Hockey Superleague, hadPlayoffFinalsWeekend, true]
-
A.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
B.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
C.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
D.
usesPlayoffs
chosen
Indicates that a competition or league determines its final standings or champion through a postseason playoff format rather than solely by regular-season results.
-
E.
hasPlayoffMeetings
Indicates that the entities have faced each other in playoff competitions or postseason matchups.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb0647848081908d74e09f52d0919e |
completed | March 30, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:44 p.m.