Triple
T20716108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worcester Racecourse |
E509172
|
entity |
| Predicate | hasNotableRaceType |
P120070
|
FINISHED |
| Object | handicap hurdles |
—
|
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: handicap hurdles | Statement: [Worcester Racecourse, hasNotableRaceType, handicap hurdles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRaceType Context triple: [Worcester Racecourse, hasNotableRaceType, handicap hurdles]
-
A.
hasNotableRace
Indicates that an entity is associated with a race or competition that is considered notable or significant.
-
B.
notableRaceStyle
Indicates that an entity is particularly recognized for competing in, specializing in, or being associated with a specific style or category of racing.
-
C.
hasRaceFormat
chosen
Indicates that an entity is associated with, or characterized by, a particular race format or type of race structure.
-
D.
notableRacingVariant
Indicates that one entity is a particularly recognized or distinguished racing-specific version or trim of another entity.
-
E.
hasRaceClass
Indicates that an entity participates in or is associated with a particular race classification or category.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d1f3308190ae594a5b9e4ab9d5 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.