Triple

T13906257
Position Surface form Disambiguated ID Type / Status
Subject Compstall E334358 entity
Predicate nearbySettlement P350 FINISHED
Object Bredbury E67447 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: Bredbury | Statement: [Compstall, nearbySettlement, Bredbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bredbury
Context triple: [Compstall, nearbySettlement, Bredbury]
  • A. Bredbury chosen
    Bredbury is a suburban town in Greater Manchester, England, situated near Stockport and known for its residential character and local industrial heritage.
  • B. Prestbury
    Prestbury is an affluent village in Cheshire, England, known for its exclusive residential character and inclusion in the wealthy Cheshire Golden Triangle.
  • C. Bredbury Hall
    Bredbury Hall is a historic country house and former hotel and nightclub located in Bredbury, near Stockport in Greater Manchester, England.
  • D. Pendlebury
    Pendlebury is a suburban area in the City of Salford, Greater Manchester, England, historically known for its coal mining and textile industries.
  • E. Samlesbury
    Samlesbury is a village in Lancashire, England, known for its historic Samlesbury Hall and its location near the River Ribble.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de25dc26cc8190a7909980b1d34933 completed April 14, 2026, 11:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69fba1c26ba08190b19560123691fda4 completed May 6, 2026, 8:17 p.m.
Created at: April 9, 2026, 10:16 p.m.