Triple
T12829783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goal of the Century |
E306752
|
entity |
| Predicate | tournamentOutcomeForMaradona |
P107110
|
FINISHED |
| Object | World Cup winner |
—
|
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: World Cup winner | Statement: [Goal of the Century, tournamentOutcomeForMaradona, World Cup winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentOutcomeForMaradona Context triple: [Goal of the Century, tournamentOutcomeForMaradona, World Cup winner]
-
A.
notableWorldCupFinish
Indicates that an entity achieved a significant or distinguished placement or result in a FIFA World Cup tournament.
-
B.
copaAmerica2016FinalResult
Indicates the outcome or final score of the Copa América 2016 championship match between the competing teams.
-
C.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
D.
copaAmerica2015FinalResult
Indicates the outcome or final score of the 2015 Copa América tournament’s championship match.
-
E.
wonCopaDelRey
Indicates that one entity achieved victory in the Copa del Rey competition over another entity or in a specific edition of the tournament.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:34 p.m.