Triple
T28570056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 Canada Cup |
E722787
|
entity |
| Predicate | decisiveGoalGame |
P168626
|
FINISHED |
| Object | Game 3 of the final |
—
|
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: Game 3 of the final | Statement: [1987 Canada Cup, decisiveGoalGame, Game 3 of the final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveGoalGame Context triple: [1987 Canada Cup, decisiveGoalGame, Game 3 of the final]
-
A.
decidingGameOf
Indicates that one event, action, or game serves as the decisive factor determining the outcome or result of another.
-
B.
decisiveMatchOf
Indicates that one entity is a match for another in a way that determines or strongly influences a final outcome or decision.
-
C.
decisiveGameVenue
Indicates the location where the final, outcome-determining game of a series or competition is held.
-
D.
decidingGoalMinute
Indicates the minute in a match when a goal is scored that ultimately decides the outcome (e.g., the winning or decisive goal).
-
E.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
- F. None of above. chosen
Provenance (4 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_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 28, 2026, 4:09 a.m.