Triple

T17441575
Position Surface form Disambiguated ID Type / Status
Subject Okehampton railway station E424666 entity
Predicate servedArea P82 FINISHED
Object Okehampton 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: Okehampton | Statement: [Okehampton railway station, servedArea, Okehampton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Okehampton
Context triple: [Okehampton railway station, servedArea, Okehampton]
  • A. Okehampton chosen
    Okehampton is a historic market town in Devon, England, known for its medieval castle and role as a former parliamentary borough.
  • B. Cullompton
    Cullompton is a historic market town in Devon, England, known for its agricultural heritage and location in the Culm Valley.
  • C. Sompting
    Sompting is a village and civil parish in West Sussex, England, situated near the south coast between Worthing and Lancing.
  • D. Quidhampton
    Quidhampton is a small village in Wiltshire, England, situated just west of Salisbury.
  • E. Cinderford
    Cinderford is a small industrial town in Gloucestershire, England, historically associated with coal mining and situated within the Forest of Dean.
  • 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_69d889db0ba481908402409af3b37917 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e44ff75538819083f77756d39a1aaa completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 5:46 a.m.