Triple
T18183068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsom Derby Festival |
E435338
|
entity |
| Predicate | mainRaceSurface |
P50583
|
FINISHED |
| Object | turf |
—
|
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: turf | Statement: [Epsom Derby Festival, mainRaceSurface, turf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRaceSurface Context triple: [Epsom Derby Festival, mainRaceSurface, turf]
-
A.
hasRaceSurface
chosen
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
B.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
C.
hasCourtSurface
Indicates that something (such as a court or playing area) possesses a specific type of surface.
-
D.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
E.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffc432c8190af53da5256dc476c |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.