Triple

T19956788
Position Surface form Disambiguated ID Type / Status
Subject Sulby E479703 entity
Predicate hasLandmark P105 FINISHED
Object Sulby Bridge 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: Sulby Bridge | Statement: [Sulby, hasLandmark, Sulby Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sulby Bridge
Context triple: [Sulby, hasLandmark, Sulby Bridge]
  • A. Sulby Bridge chosen
    Sulby Bridge is a well-known road bridge on the Isle of Man, recognized as a landmark section of the Snaefell Mountain Course used for the Isle of Man TT motorcycle races.
  • B. Lazonby Bridge
    Lazonby Bridge is a historic stone road bridge spanning the River Eden near the village of Lazonby in Cumbria, England.
  • C. Wetherby Bridge
    Wetherby Bridge is a historic stone road bridge spanning the River Wharfe in the market town of Wetherby, West Yorkshire, England.
  • D. Bainsford Bridge
    Bainsford Bridge is a road and pedestrian bridge in Bainsford, Falkirk, Scotland, spanning the Forth and Clyde Canal and serving as a key local transport link.
  • E. Helwith Bridge
    Helwith Bridge is a small village in North Yorkshire, England, situated in the scenic Ribblesdale valley of the Yorkshire Dales.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65af08e008190a3a1b807b638a99e completed April 20, 2026, 4:57 p.m.
Created at: April 10, 2026, 1:54 p.m.