Triple

T22742180
Position Surface form Disambiguated ID Type / Status
Subject Clayton, Greater Manchester E562441 entity
Predicate near P350 FINISHED
Object Droylsden 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: Droylsden | Statement: [Clayton, Greater Manchester, near, Droylsden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Droylsden
Context triple: [Clayton, Greater Manchester, near, Droylsden]
  • A. Droylsden chosen
    Droylsden is a town in Greater Manchester, England, historically part of Lancashire and now a residential suburb of Manchester.
  • B. Levenshulme
    Levenshulme is a residential suburb in south Manchester, England, known for its diverse community and vibrant local markets.
  • C. Pelsall
    Pelsall is a suburban village in the West Midlands of England, known for its residential character and local community amenities within the wider Walsall area.
  • D. Worsley
    Worsley is a village in Greater Manchester, England, historically significant as a coal-mining and canal hub central to the early Industrial Revolution.
  • E. Didsbury
    Didsbury is a small town in central Alberta, Canada, known for its agricultural roots and location along major regional transportation routes.
  • 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_69e245513a5c81908d5cb471b4fc429d completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1797400fc8190bec26726f434f787 completed April 29, 2026, 3:22 a.m.
Created at: April 17, 2026, 3:23 p.m.