Triple
T15260323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musselburgh Racecourse |
E364756
|
entity |
| Predicate | racecourseSurface |
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: [Musselburgh Racecourse, racecourseSurface, turf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racecourseSurface Context triple: [Musselburgh Racecourse, racecourseSurface, turf]
-
A.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
B.
hasRaceSurface
chosen
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
C.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
D.
racecourseCounty
Indicates the county in which a given racecourse is geographically located or administered.
-
E.
racecourseManaged
Indicates that one entity is responsible for operating, organizing, or overseeing the management of a racecourse for another 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084e85a08190b8e63598b9f6a535 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.