Triple
T24564407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Push It |
E607742
|
entity |
| Predicate | hasJockey |
P156348
|
FINISHED |
| Object | AP McCoy |
—
|
NE NERFINISHED |
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: AP McCoy | Statement: [Don't Push It, hasJockey, AP McCoy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJockey Context triple: [Don't Push It, hasJockey, AP McCoy]
-
A.
hasNotableJockey
Indicates that an entity (typically a racehorse) is or was ridden by a jockey who is considered notable or distinguished.
-
B.
hasJockeyRidingStyle
Indicates that a jockey is associated with a particular riding style they use during races.
-
C.
hasRacehorseCharacter
Indicates that one entity possesses the traits, qualities, or behavioral characteristics associated with a racehorse in relation to another entity or context.
-
D.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
-
E.
hasOwnerRider
Indicates that an entity (such as an animal or vehicle) has a specific person who both owns it and rides or uses it.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f9d0f881909afc04537c32f76b |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:28 a.m.