Triple

T18719751
Position Surface form Disambiguated ID Type / Status
Subject Rovers E457737 entity
Predicate cityDerby P10824 FINISHED
Object Hull Derby 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: Hull Derby | Statement: [Rovers, cityDerby, Hull Derby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hull Derby
Context triple: [Rovers, cityDerby, Hull Derby]
  • A. Hull Derby chosen
    Hull Derby is the fiercely contested rugby league rivalry match between Hull F.C. and Hull Kingston Rovers, two neighboring clubs from the city of Hull in England.
  • B. M1 derby
    The M1 derby is an English football rivalry match contested between Watford F.C. and Luton Town, named after the motorway that links the two clubs' home towns.
  • C. Bristol derby
    The Bristol derby is a fiercely contested local football rivalry between the city’s two main clubs, Bristol City and Bristol Rovers.
  • D. Yorkshire derby
    The Yorkshire derby is a fiercely contested football rivalry between clubs from the historic English county of Yorkshire, marked by intense local pride and regional bragging rights.
  • E. Tees–Wear derby
    The Tees–Wear derby is an English football rivalry contested between Sunderland A.F.C. and Middlesbrough F.C., reflecting regional competition between the Wearside and Teesside areas in North East England.
  • 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_69d8d393ba9c8190a8b03b04ddbb0a09 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e56ab9e0dc8190bf579d7e89e941f4 completed April 19, 2026, 11:52 p.m.
Created at: April 10, 2026, 11:50 a.m.