Triple
T23725235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayr Gold Cup |
E586254
|
entity |
| Predicate | sprintCategory |
P1907
|
FINISHED |
| Object | 6-furlong handicap |
—
|
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: 6-furlong handicap | Statement: [Ayr Gold Cup, sprintCategory, 6-furlong handicap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sprintCategory Context triple: [Ayr Gold Cup, sprintCategory, 6-furlong handicap]
-
A.
isSprint
Indicates that an entity represents a short, time-boxed iteration or development cycle within a larger project or process.
-
B.
recordSpeedCategory
Indicates the classification of an entity’s speed into a predefined category (e.g., slow, normal, fast) based on its recorded speed.
-
C.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
D.
sportCategory
chosen
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
E.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b914adc08190b339c7f83f1536d7 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:08 p.m.