Triple

T9389873
Position Surface form Disambiguated ID Type / Status
Subject Windermere branch line E225998 entity
Predicate serves P98 FINISHED
Object Burneside E319958 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: Burneside | Statement: [Windermere branch line, serves, Burneside]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burneside
Context triple: [Windermere branch line, serves, Burneside]
  • A. Burneside chosen
    Burneside is a small village in Cumbria, England, known for its riverside setting near Kendal and its historic paper mill industry.
  • B. Silloth
    Silloth is a small coastal town in Cumbria, England, known for its Victorian-era seaside promenade and views across the Solway Firth to Scotland.
  • C. Gisburn
    Gisburn is a small rural village and civil parish in Lancashire, England, situated within the Ribble Valley district.
  • D. Ryhope
    Ryhope is a coastal village and suburb of Sunderland in North East England, historically rooted in coal mining and agriculture.
  • E. Castlerock
    Castlerock is a small seaside village and popular holiday resort on the north coast of Northern Ireland.
  • 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_69ca842f7e3481908bf5bcf52e032dbd completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd50d83c188190925c389dff1341b0 completed April 1, 2026, 5:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69d100f86bac8190a26ab156f24455bb completed April 4, 2026, 12:15 p.m.
Created at: March 30, 2026, 7:45 p.m.