Triple

T5187982
Position Surface form Disambiguated ID Type / Status
Subject Frodsham railway station E117078 entity
Predicate serves P98 FINISHED
Object Frodsham E325571 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: Frodsham | Statement: [Frodsham railway station, serves, Frodsham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frodsham
Context triple: [Frodsham railway station, serves, Frodsham]
  • A. Frodsham chosen
    Frodsham is a historic market town in Cheshire, England, known for its scenic setting near the River Mersey and surrounding hills.
  • B. Sandbach
    Sandbach is a historic market town in Cheshire, England, noted for its Saxon crosses and traditional town centre.
  • C. Winsford
    Winsford is a town in Cheshire, England, known historically for its salt mining industry and its location along the River Weaver.
  • D. Knutsford
    Knutsford is a historic market town in Cheshire, England, known for its picturesque streets, affluent character, and literary associations with Elizabeth Gaskell.
  • E. Nantwich
    Nantwich is a historic market town in northwest England known for its well-preserved Tudor and Georgian architecture and long association with the salt industry.
  • 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_69bd44620ff48190bcac01782107a397 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd79c56280819085926316f7b520bc completed March 20, 2026, 4:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69beefb6eaac8190a34b01c6e30b41dc completed March 21, 2026, 7:21 p.m.
Created at: March 20, 2026, 1:46 p.m.