Triple

T13149458
Position Surface form Disambiguated ID Type / Status
Subject Exeter to Barnstaple line E312424 entity
Predicate hasStation P35 FINISHED
Object Chapelton E644484 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: Chapelton | Statement: [Exeter to Barnstaple line, hasStation, Chapelton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chapelton
Context triple: [Exeter to Barnstaple line, hasStation, Chapelton]
  • A. Chapelton chosen
    Chapelton is a small rural settlement in Devon, England, known for its location on the Tarka Line railway route.
  • B. Chalkwell
    Chalkwell is a coastal suburb of Southend-on-Sea in Essex, England, known for its seafront, park, and residential character.
  • C. Newchapel
    Newchapel is a small village located within the Tandridge District of Surrey in South East England.
  • D. Cheriton
    Cheriton is a suburban area of Folkestone in Kent, England, known for its residential character and proximity to the Channel Tunnel terminal.
  • E. Churwell
    Churwell is a village and suburb in West Yorkshire, England, situated near the town of Morley within the City of Leeds metropolitan area.
  • 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_69d806aabde48190899e13e41659cae5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98bd1fc408190b4b5ca973bcee403 completed April 10, 2026, 11:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6f5da0f708190b848601e571a9fff completed May 3, 2026, 7:14 a.m.
Created at: April 9, 2026, 9:11 p.m.