Triple

T14933704
Position Surface form Disambiguated ID Type / Status
Subject Potters Bar railway station E372335 entity
Predicate locatedIn P40 FINISHED
Object Potters Bar 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: Potters Bar | Statement: [Potters Bar railway station, locatedIn, Potters Bar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Potters Bar
Context triple: [Potters Bar railway station, locatedIn, Potters Bar]
  • A. Potters Bar chosen
    Potters Bar is a commuter town in southern England, located just north of London and known for its residential character and transport links.
  • B. Bennetts End
    Bennetts End is a residential area and suburb located within the county of Hertfordshire in England.
  • C. Leverstock Green
    Leverstock Green is a suburban village and residential area on the outskirts of Hemel Hempstead in Hertfordshire, England.
  • D. Harmondsworth
    Harmondsworth is a village in the London Borough of Hillingdon, England, known for its historic Great Barn and proximity to Heathrow Airport.
  • E. Datchet
    Datchet is a riverside village and civil parish in Berkshire, England, situated on the River Thames near Windsor.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded646a0808190ba5c0c91bde011c5 completed April 15, 2026, 12:05 a.m.
Created at: April 10, 2026, 2:37 a.m.