Triple

T20114849
Position Surface form Disambiguated ID Type / Status
Subject Fishersgate railway station E490430 entity
Predicate serves P98 FINISHED
Object Fishersgate 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: Fishersgate | Statement: [Fishersgate railway station, serves, Fishersgate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fishersgate
Context triple: [Fishersgate railway station, serves, Fishersgate]
  • A. Fishersgate chosen
    Fishersgate is a small coastal residential area in West Sussex, England, situated between Southwick and Portslade on the south coast.
  • B. Fisherrow
    Fisherrow is a coastal area and former fishing village that forms part of Musselburgh in East Lothian, Scotland.
  • C. Greenside
    Greenside is a leafy, upmarket residential and dining suburb in northern Johannesburg, South Africa, known for its vibrant restaurants and cafes.
  • D. Oughterside
    Oughterside is a small village in Cumbria, England, situated within the borough of Allerdale.
  • E. Waterhead
    Waterhead is a residential district within the town of Oldham in Greater Manchester, England.
  • 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_69da62636cc08190982cc71733a17b8d completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e666e3f2288190840d1eb431ac9a1b completed April 20, 2026, 5:48 p.m.
Created at: April 11, 2026, 11:29 p.m.