Triple

T4398370
Position Surface form Disambiguated ID Type / Status
Subject Hull Paragon Interchange E99548 entity
Predicate hasServiceTo P6787 FINISHED
Object Beverley E406105 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: Beverley | Statement: [Hull Paragon Interchange, hasServiceTo, Beverley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beverley
Context triple: [Hull Paragon Interchange, hasServiceTo, Beverley]
  • A. Beverley chosen
    Beverley is a historic market town and civil parish in the East Riding of Yorkshire, England, known for its impressive Gothic minster and medieval architecture.
  • B. Yorkton
    Yorkton is a small city in southeastern Saskatchewan, Canada, known as a regional hub for agriculture and services.
  • C. Bakewell
    Bakewell is a historic market town in Derbyshire, England, famed for its traditional Bakewell pudding and its picturesque setting in the Peak District.
  • D. Northbourne
    Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
  • E. Brough
    Brough is a village and civil parish in the East Riding of Yorkshire, England, situated on the northern bank of the Humber Estuary.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69b345506b408190b0e3dee616738a7d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b352adce588190b9e6ed53458aa1e1 completed March 12, 2026, 11:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5e53ae7bc8190b216319e522b11c6 completed March 14, 2026, 10:46 p.m.
Created at: March 12, 2026, 11:20 p.m.