Triple
T19794553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 6 double-overtime game |
E475505
|
entity |
| Predicate | overtimes |
P5853
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Game 6 double-overtime game, overtimes, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overtimes Context triple: [Game 6 double-overtime game, overtimes, 2]
-
A.
overtimePlayed
chosen
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
B.
usesOvertime
Indicates that one entity makes use of another entity repeatedly or continuously over an extended period of time.
-
C.
game7Overtimes
Indicates that a game extended into a seventh overtime period, reflecting an exceptionally prolonged and closely contested match.
-
D.
allowsOvertime
Indicates that one entity permits another entity to work beyond standard or scheduled time limits.
-
E.
longestGameOvertimes
Indicates the number of overtime periods played in the longest game (by duration or overtime count) within a given context.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c5a7d48190b2a384f768d13750 |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.