Triple
T21274939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mánes Bridge |
E524364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Prague |
C37129
|
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 Prague Context triple: [Mánes Bridge, instanceOf, bridge in Prague]
-
A.
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.
-
B.
landmark in Prague
chosen
A landmark in Prague is a notable physical site or structure—such as a historic building, bridge, square, or monument—recognized for its cultural, architectural, or historical significance within the city.
-
C.
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.
-
D.
road in Prague
A road in Prague is a public thoroughfare within the city’s urban fabric that supports vehicular and pedestrian movement while reflecting the historical layout, architectural context, and transportation infrastructure of the Czech capital.
-
E.
bridge in Vilnius
A bridge in Vilnius is a structural crossing over the Neris or other local waterways that connects different parts of the city, facilitating transportation, pedestrian movement, and urban integration.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:01 p.m.