Triple
T37705624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwedenbrücke |
E939190
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Vienna |
C65918
|
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 Vienna Context triple: [Schwedenbrücke, instanceOf, bridge in Vienna]
-
A.
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.
-
B.
bridge in Budapest
A bridge in Budapest is a structural crossing over the Danube River that connects the city’s Buda and Pest sides, serving both as vital transportation infrastructure and as an iconic architectural landmark.
-
C.
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.
-
D.
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.
-
E.
bridge in Copenhagen
A bridge in Copenhagen is a structural crossing—often designed for pedestrians, cyclists, and vehicles—that spans waterways or roads within the city, integrating functional transport with characteristic Danish urban and architectural aesthetics.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.