Triple

T2094343
Position Surface form Disambiguated ID Type / Status
Subject Leatherhead E32744 entity
Predicate hasRiverCrossing P1970 FINISHED
Object Leatherhead Bridge E95381 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: Leatherhead Bridge | Statement: [Leatherhead, hasRiverCrossing, Leatherhead Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leatherhead Bridge
Context triple: [Leatherhead, hasRiverCrossing, Leatherhead Bridge]
  • A. Leatherhead Bridge chosen
    Leatherhead Bridge is a historic road bridge spanning the River Mole in Leatherhead, Surrey, England.
  • B. Sandfield Bridge
    Sandfield Bridge is a road bridge spanning the Gloucester and Sharpness Canal in Gloucestershire, England.
  • C. Whaley Bridge
    Whaley Bridge is a small town in the High Peak district of Derbyshire, England, known historically for its role in the canal and textile industries.
  • D. Runnymede Bridge
    Runnymede Bridge is a road bridge over the River Thames in Surrey, England, carrying the M25 motorway near the historic meadow of Runnymede.
  • E. Burton Bridge
    Burton Bridge is a historic road bridge in Burton upon Trent, Staffordshire, England, known for carrying traffic across the River Trent and shaping the town’s development.
  • 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_69a885eba0708190999696a45cbec816 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abba98c32081908a243bc7088a1510 completed March 7, 2026, 5:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69b24a9a49e481908f1916cbff31d908 completed March 12, 2026, 5:09 a.m.
Created at: March 4, 2026, 7:43 p.m.