Triple

T3354379
Position Surface form Disambiguated ID Type / Status
Subject Manchester urban area E70570 entity
Predicate hasMajorSettlement P316 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: [Manchester urban area, hasMajorSettlement, Poynton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poynton
Context triple: [Manchester urban area, hasMajorSettlement, 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. Wilcote
    Wilcote is a small rural village in the district of West Oxfordshire in Oxfordshire, England.
  • C. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • D. Pirton
    Pirton is a rural village and civil parish in North Hertfordshire, England, known for its historic buildings and surrounding countryside.
  • E. Repton
    Repton is a historic English village in Derbyshire best known for its ancient abbey and prestigious Repton School.
  • 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_69ad85a4ef7c8190a29e2bbd6fa454e4 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb24036848190bac779d17dfdce3b completed March 8, 2026, 5:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69b325373a1c8190b26d883e2f0dd92b completed March 12, 2026, 8:42 p.m.
Created at: March 8, 2026, 3:13 p.m.