Triple

T27120173
Position Surface form Disambiguated ID Type / Status
Subject Bryghusbroen E686973 entity
Predicate instanceOf P0 FINISHED
Object bridge in Copenhagen C52504 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 Copenhagen
Context triple: [Bryghusbroen, instanceOf, bridge in Copenhagen]
  • A. 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.
  • B. bridge in Sweden
    A bridge in Sweden is a constructed structure that spans physical obstacles such as water or valleys within Swedish territory, facilitating transportation and connectivity while adhering to local engineering standards and environmental considerations.
  • C. bridge in Norway
    A bridge in Norway is a structural crossing—often spanning fjords, rivers, or valleys—designed to connect remote or separated areas while withstanding harsh Nordic weather and integrating with the surrounding natural landscape.
  • D. 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.
  • E. 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.
  • 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_69ef148c2b588190afc15b529f7af845 completed April 27, 2026, 7:47 a.m.
Created at: April 27, 2026, 8:58 a.m.