Triple

T3761592
Position Surface form Disambiguated ID Type / Status
Subject Ludlow E82172 entity
Predicate hasLandmark P105 FINISHED
Object Dinham Bridge E391982 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: Dinham Bridge | Statement: [Ludlow, hasLandmark, Dinham Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dinham Bridge
Context triple: [Ludlow, hasLandmark, Dinham Bridge]
  • A. Dinham Bridge chosen
    Dinham Bridge is a historic stone arch bridge in Ludlow, Shropshire, England, known for carrying traffic across the River Teme near Ludlow Castle.
  • B. Hodder Bridge
    Hodder Bridge is a road bridge in Lancashire, England, that carries traffic across the River Hodder in the Ribble Valley.
  • C. Nowra Bridge
    Nowra Bridge is a key road bridge spanning the Shoalhaven River in Nowra, New South Wales, Australia, serving as an important transport link for the region.
  • D. Morrison Bridge
    The Morrison Bridge is a bascule bridge spanning the Willamette River in downtown Portland, Oregon, carrying both vehicle and pedestrian traffic.
  • E. Bridgewater Bridge
    Bridgewater Bridge is a major road and rail swing bridge in Tasmania, Australia, spanning the Derwent River and serving as a key transport link north of Hobart.
  • 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_69ad8b1db40081908b61ffa6b78afd4d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcbc553a08190ba361675901496ed completed March 8, 2026, 7:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf3a763c5081909cfb4b209207c859 completed March 22, 2026, 12:40 a.m.
Created at: March 8, 2026, 3:35 p.m.