Triple

T20748495
Position Surface form Disambiguated ID Type / Status
Subject Manchester to Chester line E510651 entity
Predicate via P5680 FINISHED
Object Mouldsworth 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: Mouldsworth | Statement: [Manchester to Chester line, via, Mouldsworth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mouldsworth
Context triple: [Manchester to Chester line, via, Mouldsworth]
  • A. Mouldsworth chosen
    Mouldsworth is a village in Cheshire, England, served by a railway station on the Manchester–Chester line.
  • B. Minworth
    Minworth is a suburban village in the north-east of Birmingham, England, known for its industrial estates, residential areas, and proximity to major transport routes.
  • C. Minstead
    Minstead is a small village in Hampshire, England, best known as the burial place of Sir Arthur Conan Doyle.
  • D. Blisworth
    Blisworth is a village in Northamptonshire, England, known for its historic location on the Grand Union Canal near the Blisworth Tunnel.
  • E. Knaphill
    Knaphill is a suburban village in Surrey, England, forming part of the borough of Woking.
  • 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_69e0b4c845e88190b4c5f3ae79291182 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c228af288190a20829d45c034c24 completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:34 p.m.