Triple
T25923530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ada Bridge |
E653238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Belgrade |
C50091
|
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 Belgrade Context triple: [Ada Bridge, instanceOf, bridge in Belgrade]
-
A.
bridge in Croatia
A bridge in Croatia is a structural crossing—such as a road, rail, or pedestrian span—located within Croatian territory, designed to connect separated land areas over obstacles like water, valleys, or other infrastructure.
-
B.
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.
-
C.
Ottoman bridge
An Ottoman bridge is a stone or masonry arch bridge built during the Ottoman Empire, typically featuring elegant arches, narrow decks, and often serving as both a transportation route and a social or commercial gathering space.
-
D.
bridge in Moscow
A bridge in Moscow is a structural crossing over the Moskva River or other waterways in the city, serving both transportation needs and often acting as an architectural landmark within the urban landscape.
-
E.
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.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:35 a.m.