Triple

T3354373
Position Surface form Disambiguated ID Type / Status
Subject Manchester urban area E70570 entity
Predicate hasMajorSettlement P316 FINISHED
Object Royton E83854 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: Royton | Statement: [Manchester urban area, hasMajorSettlement, Royton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Royton
Context triple: [Manchester urban area, hasMajorSettlement, Royton]
  • A. Royton chosen
    Royton is a town in Greater Manchester, England, historically part of Lancashire and now within the Metropolitan Borough of Oldham.
  • B. 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.
  • C. Droitwich
    Droitwich is a historic spa town in Worcestershire, England, long known for its salt springs and brine baths.
  • D. Shevington
    Shevington is a village and civil parish in the Metropolitan Borough of Wigan, Greater Manchester, England.
  • E. Redditch
    Redditch is a town in the county of Worcestershire in England, historically known for its needle-making industry and now a modern residential and commercial center.
  • 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.