Triple
T28570060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 Canada Cup |
E722787
|
entity |
| Predicate | decisiveGoalTimeRemaining |
P7561
|
FINISHED |
| Object | 1:26 |
—
|
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: 1:26 | Statement: [1987 Canada Cup, decisiveGoalTimeRemaining, 1:26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveGoalTimeRemaining Context triple: [1987 Canada Cup, decisiveGoalTimeRemaining, 1:26]
-
A.
decidingGoalMinute
Indicates the minute in a match when a goal is scored that ultimately decides the outcome (e.g., the winning or decisive goal).
-
B.
decisiveGoalGame
Indicates that a game contains a goal or scoring event that definitively determines the winner or final outcome.
-
C.
decidingScoreTime
Indicates the point in time at which a decisive or game-determining score occurs.
-
D.
gameWinningScoreTimeRemaining
chosen
Indicates the amount of time left in the game when the decisive, game-winning score was made.
-
E.
goalTimeRecord
Indicates that a specific time value is recorded as the target or goal duration for an activity or process.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 4:09 a.m.