Triple
T32317663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashland Stakes |
E825683
|
entity |
| Predicate | isPrepRaceFor |
P2534
|
FINISHED |
| Object | Kentucky Oaks |
—
|
NE NERFINISHED |
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: Kentucky Oaks | Statement: [Ashland Stakes, isPrepRaceFor, Kentucky Oaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrepRaceFor Context triple: [Ashland Stakes, isPrepRaceFor, Kentucky Oaks]
-
A.
isPreparedAs
Indicates that one entity is made ready, arranged, or configured in a particular way or form as specified by another entity.
-
B.
isRelayRace
Indicates that the activity or event is a relay race, where multiple participants or teams take turns completing segments of a race in sequence.
-
C.
isInauguralRace
Indicates that the race is the first-ever or opening event in a series, season, or competition.
-
D.
preparesFor
chosen
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
E.
isSprintChampionshipRace
Indicates that the race is designated as the sprint championship event within a competition or season.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdbc092c81908d93b4c4a4899cde |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:46 a.m.