Triple
T4509588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronation Cup |
E102015
|
entity |
| Predicate | racecourseStraight |
P55669
|
FINISHED |
| Object | partly downhill then uphill finish |
—
|
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: partly downhill then uphill finish | Statement: [Coronation Cup, racecourseStraight, partly downhill then uphill finish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racecourseStraight Context triple: [Coronation Cup, racecourseStraight, partly downhill then uphill finish]
-
A.
racecourseFeature
chosen
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
B.
racecourseCounty
Indicates the county in which a given racecourse is geographically located or administered.
-
C.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
D.
raceDirection
Indicates the directional orientation or path along which a race or racing event proceeds.
-
E.
racecourseRegion
Indicates that a racecourse is located within, or associated with, a particular geographic or administrative region.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd571138b88190b68bbfc4300aaf9d |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.