Triple
T6313048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uttoxeter |
E141549
|
entity |
| Predicate | racecourseType |
P69994
|
FINISHED |
| Object | National Hunt racecourse |
—
|
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: National Hunt racecourse | Statement: [Uttoxeter, racecourseType, National Hunt racecourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racecourseType Context triple: [Uttoxeter, racecourseType, National Hunt racecourse]
-
A.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
B.
raceTypeDetail
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
C.
racecourseCounty
Indicates the county in which a given racecourse is geographically located or administered.
-
D.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
E.
raceTypeHosted
Indicates that a particular type of race is organized or held by a given host or organizing entity.
- F. None of above. chosen
Provenance (4 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0649ea98c819086509e175812c6c0 |
completed | March 22, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:28 p.m.