Triple

T18791920
Position Surface form Disambiguated ID Type / Status
Subject Over Alderley E459534 entity
Predicate near P350 FINISHED
Object Wilmslow 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: Wilmslow | Statement: [Over Alderley, near, Wilmslow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wilmslow
Context triple: [Over Alderley, near, Wilmslow]
  • A. Wilmslow chosen
    Wilmslow is an affluent town in Cheshire, England, known for its prosperous residential areas and location within the Greater Manchester commuter belt.
  • B. Rothwell
    Rothwell is a town in Northamptonshire, England, situated near Kettering and known for its historic market heritage.
  • C. Rothwell
    Rothwell is a town in West Yorkshire, England, situated near Leeds and historically known for its coal mining and market traditions.
  • D. Rothwell
    Rothwell is a residential suburb located within Queensland’s Moreton Bay Region, north of Brisbane, Australia.
  • E. Northwich
    Northwich is a historic market and industrial town in Cheshire, England, traditionally known for its salt mining and chemical industries.
  • 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_69d8d396f54c8190ba49db31e8743842 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5978665388190aaefed0ec30a1ff3 completed April 20, 2026, 3:03 a.m.
Created at: April 10, 2026, 11:53 a.m.