Triple

T17933485
Position Surface form Disambiguated ID Type / Status
Subject Betfair Chase E448392 entity
Predicate racecourse P16266 FINISHED
Object Haydock Park 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: Haydock Park | Statement: [Betfair Chase, racecourse, Haydock Park]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haydock Park
Context triple: [Betfair Chase, racecourse, Haydock Park]
  • A. Paddock Park
    Paddock Park is a local public park in Havertown, Pennsylvania, offering green space and recreational amenities for neighborhood residents.
  • B. Hall Park
    Hall Park is a small town located within Cleveland County in the U.S. state of Oklahoma.
  • C. Haydock Park Racecourse chosen
    Haydock Park Racecourse is a prominent British horse racing venue in Merseyside, known for hosting both flat and National Hunt racing, including major events like the Betfair Chase.
  • D. Hallwood Park
    Hallwood Park is a residential area in Runcorn, Cheshire, England, forming part of the town’s New Town developments.
  • E. Kempton Park
    Kempton Park is a town on the East Rand in Gauteng, South Africa, known for housing OR Tambo International Airport and being part of the greater Johannesburg metropolitan area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4a5547b7881909dc41bb7dd34194f completed April 19, 2026, 9:50 a.m.
Created at: April 10, 2026, 10:21 a.m.