Triple

T9496734
Position Surface form Disambiguated ID Type / Status
Subject 1831 London Bridge E229026 entity
Predicate instanceOf P0 FINISHED
Object former bridge in London C2690 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: former bridge in London
Context triple: [1831 London Bridge, instanceOf, former bridge in London]
  • A. bridge in London
    A bridge in London is a structural crossing over the River Thames or other waterways in the city, designed to support vehicular, rail, or pedestrian traffic while integrating with the historic and urban landscape.
  • B. Seine bridge
    A Seine bridge is a structure that spans the River Seine, providing a crossing for pedestrians, vehicles, or trains while often serving as an architectural and cultural landmark within its urban setting.
  • C. iron bridge
    An iron bridge is a structural crossing composed primarily of iron elements, designed to span physical obstacles such as rivers or valleys while supporting loads like vehicles, pedestrians, or trains.
  • D. former bridge chosen
    A former bridge is a structure that once functioned as a crossing over an obstacle such as water, a road, or a valley, but has since been decommissioned, repurposed, or rendered unusable for its original bridging purpose.
  • E. bridge in New York City
    A bridge in New York City is a large-scale transportation structure spanning waterways or land to connect boroughs and neighborhoods, supporting vehicular, rail, bicycle, and pedestrian traffic within the city’s dense urban environment.
  • F. None of above.

Provenance (1 batch)

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_69ca84753660819098e8d416e89e26ae completed March 30, 2026, 2:11 p.m.
Created at: March 30, 2026, 7:56 p.m.