Triple

T5191617
Position Surface form Disambiguated ID Type / Status
Subject Tideswell E117167 entity
Predicate locatedNear P294 FINISHED
Object Bakewell E30940 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: Bakewell | Statement: [Tideswell, locatedNear, Bakewell]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bakewell
Context triple: [Tideswell, locatedNear, Bakewell]
  • A. Bakewell chosen
    Bakewell is a historic market town in Derbyshire, England, famed for its traditional Bakewell pudding and its picturesque setting in the Peak District.
  • B. Bedworth
    Bedworth is a small market town in Warwickshire, England, situated between Coventry and Nuneaton and known historically for coal mining and ribbon weaving.
  • C. Bolsover
    Bolsover is a historic market town in England best known for its hilltop Bolsover Castle and its location within the county of Derbyshire.
  • D. Beverley
    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.
  • E. Southwell
    Southwell is a small coastal settlement on the Isle of Portland in Dorset, England, known for its proximity to dramatic cliffs and quarrying heritage.
  • 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_69bd44620ff48190bcac01782107a397 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd79ed61c88190bda492f6489f44de completed March 20, 2026, 4:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69bef7f9a1c48190939a5073bd779be6 completed March 21, 2026, 7:56 p.m.
Created at: March 20, 2026, 1:46 p.m.