Triple
T5954724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS is Back Tournament 2020 winners |
E132483
|
entity |
| Predicate | dateOfFinal |
P14672
|
FINISHED |
| Object | 11 August 2020 |
—
|
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: 11 August 2020 | Statement: [MLS is Back Tournament 2020 winners, dateOfFinal, 11 August 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFinal Context triple: [MLS is Back Tournament 2020 winners, dateOfFinal, 11 August 2020]
-
A.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
B.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
D.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
-
E.
finalMatchDate
chosen
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.