Triple
T6685435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corner kick |
E152088
|
entity |
| Predicate | restartIfOwnGoalDirect |
P72174
|
FINISHED |
| Object | Corner kick to opponents |
—
|
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: Corner kick to opponents | Statement: [Corner kick, restartIfOwnGoalDirect, Corner kick to opponents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restartIfOwnGoalDirect Context triple: [Corner kick, restartIfOwnGoalDirect, Corner kick to opponents]
-
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.
goldenGoalRuleUsed
Indicates that the outcome of a match or competition was determined using the golden goal rule, where the first score in extra time immediately ends the game.
-
C.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
D.
scoredGameWinningGoal
Indicates that an entity scored the decisive goal that determined the final victory in a game.
-
E.
clinchingGoalPeriod
Indicates the time period or segment of play during which the decisive, game-clinching goal was scored.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cd0d939081908ede0bb6ce19f559 |
completed | March 27, 2026, 6:31 p.m. |
Created at: March 27, 2026, 2:04 p.m.