Triple
T25796309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1896 Jockey Club Stakes |
E649693
|
entity |
| Predicate | notableRacehorseInvolved |
P131366
|
FINISHED |
| Object | Sir Visto |
—
|
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: Sir Visto | Statement: [1896 Jockey Club Stakes, notableRacehorseInvolved, Sir Visto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRacehorseInvolved Context triple: [1896 Jockey Club Stakes, notableRacehorseInvolved, Sir Visto]
-
A.
notableHorse
chosen
Indicates that the subject is a horse recognized for particular significance, fame, or distinction.
-
B.
notableHorseBred
Indicates that one entity is a notable horse that was bred by the other entity.
-
C.
notableRaceTrackDepicted
Indicates that a work or representation depicts a race track that is considered notable or significant.
-
D.
notableRacingSuccess
Indicates that the subject has achieved significant or distinguished success in competitive racing events.
-
E.
notableRaceMeeting
Indicates that there is a race meeting or event that is particularly notable or significant in relation to the subject.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 22, 2026, 6:30 a.m.