Triple
T16967479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2010 |
E411577
|
entity |
| Predicate | winningGoalType |
P125425
|
FINISHED |
| Object | own goal |
—
|
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: own goal | Statement: [MLS Cup 2010, winningGoalType, own goal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winningGoalType Context triple: [MLS Cup 2010, winningGoalType, own goal]
-
A.
scoredGameWinningGoal
Indicates that an entity scored the decisive goal that determined the final victory in a game.
-
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.
goalAwarded
Indicates that a specific goal or objective has been granted or conferred upon an entity as an award or achievement.
-
D.
officialGoal
Indicates that something is the formally designated or institutionally recognized objective or target of an entity.
-
E.
ownGoalBy
Indicates that a goal was accidentally scored against a team by the specified player (i.e., the player scored an own goal).
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a6f628819080db47285954729a |
completed | April 18, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:31 a.m.