Triple
T24903257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VRC Oaks |
E623634
|
entity |
| Predicate | timingRelativeToMelbourneCup |
P47077
|
FINISHED |
| Object | run two days after the Melbourne Cup |
—
|
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 two days after the Melbourne Cup | Statement: [VRC Oaks, timingRelativeToMelbourneCup, run two days after the Melbourne Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingRelativeToMelbourneCup Context triple: [VRC Oaks, timingRelativeToMelbourneCup, run two days after the Melbourne Cup]
-
A.
BelmontStakesTime
Indicates the time at which the Belmont Stakes event takes place.
-
B.
timingOfRace
chosen
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
C.
KentuckyDerbyTime
Indicates that a specified time value corresponds to when the Kentucky Derby race takes place or took place.
-
D.
breedersCupRace
Indicates that a race is one of the official events in the Breeders' Cup horse racing series.
-
E.
racecourseOpened
Indicates that a racecourse began operating or was officially opened on a specified date or at a specified time.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:27 a.m.