Triple
T30182667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lauttasaari Bridge |
E767244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Helsinki |
C57107
|
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 Helsinki Context triple: [Lauttasaari Bridge, instanceOf, bridge in Helsinki]
-
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 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.
-
C.
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.
-
D.
bridge in Saint Petersburg
A bridge in Saint Petersburg is a structural crossing over the city's numerous rivers and canals, often featuring historic architecture, movable spans, and serving as both vital transport infrastructure and a prominent element of the urban landscape.
-
E.
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.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:26 p.m.