Triple

T25796311
Position Surface form Disambiguated ID Type / Status
Subject 1896 Jockey Club Stakes E649693 entity
Predicate partOf P40 FINISHED
Object Jockey Club Stakes
The Jockey Club Stakes is a historic British flat horse race, typically run over a middle distance at Newmarket Racecourse and contested by older thoroughbreds.
E1701310 NE 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: Jockey Club Stakes | Statement: [1896 Jockey Club Stakes, partOf, Jockey Club Stakes]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Jockey Club Stakes
Triple: [1896 Jockey Club Stakes, partOf, Jockey Club Stakes]
Generated description
The Jockey Club Stakes is a historic British flat horse race, typically run over a middle distance at Newmarket Racecourse and contested by older thoroughbreds.

Provenance (5 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_69f5ffc74fa481909b4fe24a9337f9eb completed May 2, 2026, 1:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10eca200248190a1f28f3cc9eb14d9 completed May 22, 2026, 11:54 p.m.
NEDg Description generation batch_6a10ef97dcf48190bd6b28075da6865d completed May 23, 2026, 12:06 a.m.
NED2 Entity disambiguation (via description) batch_6a10eff47f048190bb3bd46ff186889c completed May 23, 2026, 12:08 a.m.
Created at: April 22, 2026, 6:30 a.m.