Triple
T23427148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England vs Croatia (UEFA Euro 2020 Group D) |
E563223
|
entity |
| Predicate | delayedFrom |
P152233
|
FINISHED |
| Object | 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: 2020 | Statement: [England vs Croatia (UEFA Euro 2020 Group D), delayedFrom, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delayedFrom Context triple: [England vs Croatia (UEFA Euro 2020 Group D), delayedFrom, 2020]
-
A.
delayed
Indicates that an expected event, action, or outcome occurred later than its scheduled or usual time.
-
B.
delayedBy
Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
-
C.
delayedUntil
Indicates that the occurrence or effect of one event or condition is postponed and does not take place until a specified later event, time, or condition is reached.
-
D.
postponedFrom
Indicates that an event or action has been rescheduled to occur at a later time than originally planned.
-
E.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a54ae8ac8190b0bae2560582c904 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:47 p.m.