Triple

T2102712
Position Surface form Disambiguated ID Type / Status
Subject River Severn in Shrewsbury E37125 entity
Predicate crossedBy P416 FINISHED
Object Welsh Bridge E34960 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: Welsh Bridge | Statement: [River Severn in Shrewsbury, crossedBy, Welsh Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Welsh Bridge
Context triple: [River Severn in Shrewsbury, crossedBy, Welsh Bridge]
  • A. Welsh Bridge chosen
    Welsh Bridge is a historic stone arch bridge spanning the River Severn in Shrewsbury, Shropshire, England.
  • B. Pooley Bridge
    Pooley Bridge is a small Cumbrian village at the northern end of Ullswater in England’s Lake District, known as a popular tourist base for lakeside walks and boat trips.
  • C. Cobham Bridge
    Cobham Bridge is a road bridge in Surrey, England, that carries traffic across the River Mole near the village of Cobham.
  • D. Sandfield Bridge
    Sandfield Bridge is a road bridge spanning the Gloucester and Sharpness Canal in Gloucestershire, England.
  • E. St Ives Bridge
    St Ives Bridge is a historic medieval stone bridge over the River Great Ouse in St Ives, Cambridgeshire, notable for its rare surviving chapel built into the bridge.
  • 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_69a8861828948190924aa30c08806b3a completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abbabe1e9081908ea66c5406e2f1d9 completed March 7, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69b20f1577388190bc95b2151af55732 completed March 12, 2026, 12:55 a.m.
Created at: March 4, 2026, 7:43 p.m.