Triple

T13905691
Position Surface form Disambiguated ID Type / Status
Subject Bramhall E334342 entity
Predicate hasNeighbouringArea P17964 FINISHED
Object Poynton E144736 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: Poynton | Statement: [Bramhall, hasNeighbouringArea, Poynton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poynton
Context triple: [Bramhall, hasNeighbouringArea, Poynton]
  • A. Poynton chosen
    Poynton is a town in Cheshire, England, known for its former coal mining industry and distinctive shared-space central junction.
  • B. Pyrton
    Pyrton is a small rural village and civil parish in Oxfordshire, England, known for its historic church and traditional English countryside setting.
  • C. Poppleton
    Poppleton is a village and civil parish in North Yorkshire, England, situated just west of York and known for its historic character and commuter links.
  • D. Wilcote
    Wilcote is a small rural village in the district of West Oxfordshire in Oxfordshire, England.
  • E. Paulton
    Paulton is a village in Somerset, England, known historically for its coal mining and location within the Mendip district.
  • 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_69f7c724c6188190ae0c2784c3b48a12 completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:16 p.m.