Triple

T2611615
Position Surface form Disambiguated ID Type / Status
Subject Stalybridge E58786 entity
Predicate adjacentTo P224 FINISHED
Object Mossley E59151 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: Mossley | Statement: [Stalybridge, adjacentTo, Mossley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mossley
Context triple: [Stalybridge, adjacentTo, Mossley]
  • A. Mossley chosen
    Mossley is a small town in Greater Manchester, England, situated in the Tame Valley between Manchester and Huddersfield.
  • B. Arnside
    Arnside is a coastal village in Cumbria, England, known for its scenic views over Morecambe Bay and its status as a gateway to the Arnside and Silverdale Area of Outstanding Natural Beauty.
  • C. Millom
    Millom is a small coastal town in Cumbria, England, situated on the Duddon Estuary and historically known for its ironworks and mining industry.
  • D. Droylsden
    Droylsden is a town in Greater Manchester, England, historically part of Lancashire and now a residential suburb of Manchester.
  • E. 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.
  • 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_69ab4ac3523881909679750c9f8c2dec completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd87b24e48190ad1d4ce7e63c0f3e completed March 7, 2026, 7:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69af83e816808190aa2c91801fd3c6c7 completed March 10, 2026, 2:37 a.m.
Created at: March 6, 2026, 9:50 p.m.