Triple

T1003153
Position Surface form Disambiguated ID Type / Status
Subject Clifton E21647 entity
Predicate locatedNear P294 FINISHED
Object Prestwich E108630 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: Prestwich | Statement: [Clifton, locatedNear, Prestwich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prestwich
Context triple: [Clifton, locatedNear, Prestwich]
  • A. Prestwich chosen
    Prestwich is a suburban town in Greater Manchester, England, known for its residential character and proximity to Manchester city centre.
  • B. Worsley
    Worsley is a village in Greater Manchester, England, historically significant as a coal-mining and canal hub central to the early Industrial Revolution.
  • C. Urmston
    Urmston is a suburban town in Greater Manchester, England, known primarily as a residential area within the Metropolitan Borough of Trafford.
  • D. Milnrow
    Milnrow is a town in Greater Manchester, England, historically part of Lancashire and known for its textile heritage and proximity to the Pennine hills.
  • E. Timperley
    Timperley is a suburban village within the Metropolitan Borough of Trafford in Greater Manchester, England, known for its residential character and commuter links to Manchester.
  • 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_69a493c53e648190ae8cb76c433fd9a7 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b4fe0a548190aee8abf1890e141e completed March 1, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac83000d408190a79f6cdaee32b0f7 completed March 7, 2026, 7:56 p.m.
Created at: March 1, 2026, 7:41 p.m.