Triple
T3773891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2022 |
E83259
|
entity |
| Predicate | goalsInRegularTime |
P37978
|
FINISHED |
| Object | 2–2 |
—
|
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: 2–2 | Statement: [MLS Cup 2022, goalsInRegularTime, 2–2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalsInRegularTime Context triple: [MLS Cup 2022, goalsInRegularTime, 2–2]
-
A.
decidedInRegulationTime
Indicates that the outcome of a contest or match was determined within the standard allotted duration, without requiring any extra time or tiebreak procedures.
-
B.
finalScore90Minutes
chosen
Indicates the final score of a match after the standard 90 minutes of regular playing time, excluding any extra time or penalty shootouts.
-
C.
numberOfGoals
Indicates the total count of goals scored or achieved by an entity in a given context.
-
D.
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.
-
E.
penaltyShootoutScore
Indicates the number of goals each side scored during a penalty shootout used to decide a tied match.
- 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_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. |
Created at: March 8, 2026, 3:36 p.m.