Triple
T27143974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punchestown Gold Cup |
E681889
|
entity |
| Predicate | timingRelativeToCheltenham |
P161894
|
FINISHED |
| Object | run after the Cheltenham Festival |
—
|
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: run after the Cheltenham Festival | Statement: [Punchestown Gold Cup, timingRelativeToCheltenham, run after the Cheltenham Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingRelativeToCheltenham Context triple: [Punchestown Gold Cup, timingRelativeToCheltenham, run after the Cheltenham Festival]
-
A.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
B.
distanceToCheltenham
Indicates the spatial distance between a given entity and the location of Cheltenham.
-
C.
KentuckyDerbyTime
Indicates that a specified time value corresponds to when the Kentucky Derby race takes place or took place.
-
D.
racecourseCounty
Indicates the county in which a given racecourse is geographically located or administered.
-
E.
raceCheckpointFor
Indicates that something serves as a checkpoint location within the course or progression of a particular race.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c3e4bc8190af9a5d9b3c30d117 |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 9:10 a.m.