Triple
T3773892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2022 |
E83259
|
entity |
| Predicate | goalsInExtraTime |
P50847
|
FINISHED |
| Object | 1–1 |
—
|
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: 1–1 | Statement: [MLS Cup 2022, goalsInExtraTime, 1–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalsInExtraTime Context triple: [MLS Cup 2022, goalsInExtraTime, 1–1]
-
A.
finalAfterExtraTime
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
B.
penaltyShootoutScore
Indicates the number of goals each side scored during a penalty shootout used to decide a tied match.
-
C.
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.
-
D.
penaltyShootoutOccurred
Indicates that a penalty shootout took place to decide the outcome of a match or contest.
-
E.
penaltyShootoutWinner
Indicates that one competitor or team is the winner of a match decided by a penalty shootout.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc594c50819099ab5ac1b82f61a6 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:36 p.m.