Triple
T32266268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Grass Stakes |
E824294
|
entity |
| Predicate | hasRacingSurfaceHistory |
P129040
|
FINISHED |
| Object | Polytrack (historical) |
—
|
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: Polytrack (historical) | Statement: [Blue Grass Stakes, hasRacingSurfaceHistory, Polytrack (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRacingSurfaceHistory Context triple: [Blue Grass Stakes, hasRacingSurfaceHistory, Polytrack (historical)]
-
A.
hasRaceSurface
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
B.
raceSurfaceHistory
chosen
Indicates the type of surface on which an entity has raced in the past, capturing its historical race-surface conditions.
-
C.
hasRacingSurfacePreference
Indicates that an entity has a favored or typical type of racing surface on which it prefers to compete or perform.
-
D.
hasRacingUseSince
Indicates that an entity has been used for racing starting from a specified point in time.
-
E.
hasRoadHistory
Indicates that there exists a recorded history or sequence of past states, events, or changes associated with a particular road.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 12:42 a.m.