Triple

T25526663
Position Surface form Disambiguated ID Type / Status
Subject Chester May Festival E639792 entity
Predicate hasNotableRace P51905 FINISHED
Object Huxley Stakes
The Huxley Stakes is a prominent Group 2 flat horse race in Great Britain, run over middle distances and known for attracting high-quality thoroughbreds.
E1688960 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: Huxley Stakes | Statement: [Chester May Festival, hasNotableRace, Huxley 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: Huxley Stakes
Triple: [Chester May Festival, hasNotableRace, Huxley Stakes]
Generated description
The Huxley Stakes is a prominent Group 2 flat horse race in Great Britain, run over middle distances and known for attracting high-quality 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_69e75dbf3f9c8190b3f2a75d1b75d127 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f86073d0819093afb1d79b97bccc completed May 2, 2026, 1:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10c12a435081908669e6de6652ccfc completed May 22, 2026, 8:48 p.m.
NEDg Description generation batch_6a10c1a80a0081909081a3ae1b22ebf3 completed May 22, 2026, 8:50 p.m.
NED2 Entity disambiguation (via description) batch_6a10c214cc5c8190a7f5155cf346891a completed May 22, 2026, 8:52 p.m.
Created at: April 21, 2026, 3:11 p.m.