Triple
T20534266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto FC |
E504151
|
entity |
| Predicate | MLS CupFinalAppearanceYear |
P140451
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Toronto FC, MLS CupFinalAppearanceYear, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MLS CupFinalAppearanceYear Context triple: [Toronto FC, MLS CupFinalAppearanceYear, 2016]
-
A.
MLS CupFinalVenue
Indicates the venue (stadium or location) where a specific MLS Cup final match is held.
-
B.
MLS CupFinalLoser
Indicates the team that lost in the final match of a given MLS Cup competition.
-
C.
awayTeamPreviousMLS CupFinalAppearances
Indicates the number of times the away team has previously appeared in an MLS Cup final before the current match.
-
D.
MLS CupFinalCity
Indicates the city where the MLS Cup final match is held.
-
E.
MLS CupFinalScore
Indicates the final match score in a Major League Soccer (MLS) Cup championship game between the competing teams.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a06df04081908fa95c6214f06093 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:37 a.m.