Triple
T16515236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travers Stakes |
E401164
|
entity |
| Predicate | raceSurfaceCondition |
P50583
|
FINISHED |
| Object | usually fast dirt track, subject to weather |
—
|
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: usually fast dirt track, subject to weather | Statement: [Travers Stakes, raceSurfaceCondition, usually fast dirt track, subject to weather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceSurfaceCondition Context triple: [Travers Stakes, raceSurfaceCondition, usually fast dirt track, subject to weather]
-
A.
hasRaceSurface
chosen
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
B.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
C.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
D.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
E.
finalRaceWeather
Indicates the weather conditions present during the final race event.
- 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.