Triple
T15877357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wincanton Racecourse |
E384983
|
entity |
| Predicate | hostsRaceMeetingType |
P47791
|
FINISHED |
| Object | winter National Hunt meetings |
—
|
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: winter National Hunt meetings | Statement: [Wincanton Racecourse, hostsRaceMeetingType, winter National Hunt meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsRaceMeetingType Context triple: [Wincanton Racecourse, hostsRaceMeetingType, winter National Hunt meetings]
-
A.
raceTypeHosted
chosen
Indicates that a particular type of race is organized or held by a given host or organizing entity.
-
B.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
C.
raceTypeDetail
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
D.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
E.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.