Triple

T20283821
Position Surface form Disambiguated ID Type / Status
Subject Southbourne railway station E503221 entity
Predicate locatedIn P40 FINISHED
Object Southbourne 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: Southbourne | Statement: [Southbourne railway station, locatedIn, Southbourne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Southbourne
Context triple: [Southbourne railway station, locatedIn, Southbourne]
  • A. Southbourne
    Southbourne is a village and civil parish in West Sussex, England, situated near Chichester on the south coast.
  • B. Southbourne chosen
    Southbourne is a coastal suburb in the Bournemouth area of Dorset, England, known for its sandy beaches and residential character.
  • C. Northbourne
    Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
  • D. Northbourne
    Northbourne is a residential suburb within the coastal urban area of Bournemouth in Dorset, England.
  • E. Portchester
    Portchester is a village in Hampshire, England, known for its historic Roman fort and as the birthplace of author Neil Gaiman.
  • 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_69e0b4b0e79c8190bd61f22ef1329fa8 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6769049b48190bc449557b79b9e81 completed April 20, 2026, 6:55 p.m.
Created at: April 16, 2026, 10:48 a.m.