Triple

T36741014
Position Surface form Disambiguated ID Type / Status
Subject Hárosi Danube Bridge E907613 entity
Predicate instanceOf P0 FINISHED
Object bridge in Budapest C65548 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: bridge in Budapest
Context triple: [Hárosi Danube Bridge, instanceOf, bridge in Budapest]
  • A. bridge in Belgrade
    A bridge in Belgrade is a structural crossing over the Sava or Danube rivers that connects different parts of the city, facilitating transportation and symbolizing the urban and historical development of Serbia’s capital.
  • B. bridge in Helsinki
    A bridge in Helsinki is a structural crossing—often combining functional Nordic engineering with minimalist design—that spans water or land to connect different parts of the city’s urban and coastal landscape.
  • C. bridge in Salzburg
    A bridge in Salzburg is a structural crossing over the Salzach River or other local waterways that connects different parts of the city and often serves as both a transportation route and a scenic vantage point.
  • D. bridge in Venice
    A bridge in Venice is an architectural structure spanning the city’s canals, enabling pedestrian movement between separated land areas while often serving as a historic and cultural landmark.
  • E. bridge in Stockholm
    A bridge in Stockholm is a structural crossing that connects the city’s many islands and shores, facilitating transportation and integrating its urban and waterfront landscapes.
  • F. None of above. chosen

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_69f76e75aa6881909b844d00a3888ee5 completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:12 p.m.