Triple
T12191872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonín Panenka scored a chipped penalty in the shoot-out |
E290482
|
entity |
| Predicate | tookPlaceOnDate |
P6878
|
FINISHED |
| Object | 1976-06-20 |
—
|
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: 1976-06-20 | Statement: [Antonín Panenka scored a chipped penalty in the shoot-out, tookPlaceOnDate, 1976-06-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceOnDate Context triple: [Antonín Panenka scored a chipped penalty in the shoot-out, tookPlaceOnDate, 1976-06-20]
-
A.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
B.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
D.
playedOnDate
Indicates that an event or activity (such as a game, performance, or match) occurred on a specific calendar date.
-
E.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.