Triple
T12054641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game of the Century (1970 World Cup) |
E287007
|
entity |
| Predicate | scoreAfterExtraTime |
P35409
|
FINISHED |
| Object | 4–3 |
—
|
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: 4–3 | Statement: [Game of the Century (1970 World Cup), scoreAfterExtraTime, 4–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreAfterExtraTime Context triple: [Game of the Century (1970 World Cup), scoreAfterExtraTime, 4–3]
-
A.
goalsInExtraTime
Indicates that the related entity scored goals specifically during the extra time period of a match, beyond regular playing time.
-
B.
finalAfterExtraTime
chosen
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
C.
finalScore90Minutes
Indicates the final score of a match after the standard 90 minutes of regular playing time, excluding any extra time or penalty shootouts.
-
D.
penaltyShootoutScore
Indicates the number of goals each side scored during a penalty shootout used to decide a tied match.
-
E.
awayTeamEqualiserMinute
Indicates the minute of the match in which the away team scored the goal that brought the scores level.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.