Triple
T16515235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travers Stakes |
E401164
|
entity |
| Predicate | raceTiming |
P47077
|
FINISHED |
| Object | mid to late August each year |
—
|
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: mid to late August each year | Statement: [Travers Stakes, raceTiming, mid to late August each year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceTiming Context triple: [Travers Stakes, raceTiming, mid to late August each year]
-
A.
timingOfRace
chosen
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
B.
raceRecord
Indicates that there exists a recorded result or performance entry for an entity participating in a race or competitive event.
-
C.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
D.
competitionTiming
Indicates the temporal relationship or scheduling of when a competition or competitive event takes place.
-
E.
raceDayIncludes
Indicates that a particular race day schedule or event set contains or encompasses a specific race or racing-related activity.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7bbfa481909037148cdb4d8996 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.