Triple
T7463650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trotting Triple Crown |
E176315
|
entity |
| Predicate | componentRaceSurface |
P50583
|
FINISHED |
| Object | mile track (Hambletonian, Kentucky Futurity) |
—
|
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: mile track (Hambletonian, Kentucky Futurity) | Statement: [Trotting Triple Crown, componentRaceSurface, mile track (Hambletonian, Kentucky Futurity)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentRaceSurface Context triple: [Trotting Triple Crown, componentRaceSurface, mile track (Hambletonian, Kentucky Futurity)]
-
A.
hasRaceSurface
chosen
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
B.
competitionSurface
Indicates the type of surface or medium on which a competition or contest takes place.
-
C.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
D.
hasRacecourseFeature
Indicates that something possesses or includes a specific feature or characteristic related to a racecourse.
-
E.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d9d25c819087efc772b5b127fa |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.