Triple
T27231324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stayers’ Hurdle |
E682161
|
entity |
| Predicate | associatedRacecourseFeature |
P157863
|
FINISHED |
| Object | Cheltenham New Course |
—
|
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: Cheltenham New Course | Statement: [Stayers’ Hurdle, associatedRacecourseFeature, Cheltenham New Course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRacecourseFeature Context triple: [Stayers’ Hurdle, associatedRacecourseFeature, Cheltenham New Course]
-
A.
hasRacecourseFeature
Indicates that something possesses or includes a specific feature or characteristic related to a racecourse.
-
B.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
C.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
D.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
E.
racecourseUsed
chosen
Indicates that a particular racecourse is utilized or employed for a given event, activity, or purpose.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: April 27, 2026, 9:46 a.m.