Triple
T28570058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 Canada Cup |
E722787
|
entity |
| Predicate | decisiveGoalGoaltenderBeaten |
P51814
|
FINISHED |
| Object | Sergei Mylnikov |
—
|
NE NERFINISHED |
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: Sergei Mylnikov | Statement: [1987 Canada Cup, decisiveGoalGoaltenderBeaten, Sergei Mylnikov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveGoalGoaltenderBeaten Context triple: [1987 Canada Cup, decisiveGoalGoaltenderBeaten, Sergei Mylnikov]
-
A.
decisiveGoalGame
Indicates that a game contains a goal or scoring event that definitively determines the winner or final outcome.
-
B.
losingGoaltender
chosen
Indicates that a particular goaltender is the one who was in net for the team that lost the game.
-
C.
decisiveGoalScorerInFinal
Indicates that an entity scored a crucial, match-deciding goal in the final of a competition or tournament.
-
D.
scoredGoalAsGoaltender
Indicates that an entity, while playing in the role of goaltender, successfully scored a goal.
-
E.
goalkeeperAction
Indicates actions performed by a goalkeeper in the context of defending the goal, such as saving, catching, blocking, or distributing the ball.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 4:09 a.m.