Triple

T20963781
Position Surface form Disambiguated ID Type / Status
Subject Lazonby & Kirkoswald railway station E516314 entity
Predicate serves P98 FINISHED
Object Lazonby E149194 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: Lazonby | Statement: [Lazonby & Kirkoswald railway station, serves, Lazonby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lazonby
Context triple: [Lazonby & Kirkoswald railway station, serves, Lazonby]
  • A. Lazonby chosen
    Lazonby is a small rural village and civil parish in Cumbria, England, situated in the Eden Valley near the River Eden.
  • B. Cazaubon
    Cazaubon is a commune in southwestern France, known for its spa town of Barbotan-les-Thermes and its location in the Gers department of the Occitanie region.
  • C. Boddam
    Boddam is a coastal fishing village in Aberdeenshire, Scotland, known for its historic lighthouse and rugged North Sea shoreline.
  • D. Hannington
    Hannington is a small rural village in Wiltshire, England, known for its traditional English countryside setting and historic character.
  • E. Hannington
    Hannington is a small rural village in the English county of Hampshire, known for its traditional countryside setting and historic character.
  • 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_69e0b4fde6c48190af1398e7e734629e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fb71d644819087e00933fcc26217 completed April 21, 2026, 4:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a09279a50bc8190a2ac4bda770fe6fa completed May 17, 2026, 2:27 a.m.
Created at: April 16, 2026, 1:32 p.m.