Triple
T25387104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michel Plasse |
E631554
|
entity |
| Predicate | scoredGoalAsGoaltender |
P158821
|
FINISHED |
| Object | 1971-02-21 |
—
|
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: 1971-02-21 | Statement: [Michel Plasse, scoredGoalAsGoaltender, 1971-02-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoredGoalAsGoaltender Context triple: [Michel Plasse, scoredGoalAsGoaltender, 1971-02-21]
-
A.
ownGoalBy
Indicates that a goal was accidentally scored against a team by the specified player (i.e., the player scored an own goal).
-
B.
scoredGameWinningGoal
Indicates that an entity scored the decisive goal that determined the final victory in a game.
-
C.
losingGoaltender
Indicates that a particular goaltender is the one who was in net for the team that lost the game.
-
D.
goalkeeperAction
Indicates actions performed by a goalkeeper in the context of defending the goal, such as saving, catching, blocking, or distributing the ball.
-
E.
penaltyShootoutSaveBy
Indicates that a penalty kick taken during a shootout is successfully saved or stopped by a specified goalkeeper.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5656c16ac8190be99d40cb63f9541 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 1:47 p.m.