Triple
T34803425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHL regular season |
E1003280
|
entity |
| Predicate | includesShootout |
P55313
|
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: [OHL regular season, includesShootout, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesShootout Context triple: [OHL regular season, includesShootout, true]
-
A.
hasShootoutInLeague
chosen
Indicates that a league match involved a shootout (e.g., penalty or tiebreak shootout) as part of its outcome or progression.
-
B.
hasShootoutRule
Indicates that a competition, game, or match is governed by a specific rule or set of rules for resolving ties through a shootout.
-
C.
pointsForOvertimeOrShootoutWin
Indicates that a team is awarded points specifically for winning a game in overtime or a shootout.
-
D.
introducedOvertimeShootout
Indicates that an overtime shootout format was implemented or brought into use at a particular point in time.
-
E.
iceHockeySeries
Indicates a competitive sequence of related ice hockey games or matches played between the same opponents as part of a single contest or event.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.