Triple
T34465396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lansdowne Road Bridge |
E884753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Dublin |
C61599
|
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 Dublin Context triple: [Lansdowne Road Bridge, instanceOf, bridge in Dublin]
-
A.
bridge over the River Liffey
A bridge over the River Liffey is a structural crossing that spans the river in Dublin, connecting different parts of the city for pedestrians, vehicles, or public transport.
-
B.
bridge in Glasgow
A bridge in Glasgow is a structural crossing, often spanning the River Clyde, that connects different parts of the city and supports vehicular, rail, or pedestrian traffic while contributing to the urban landscape.
-
C.
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.
-
D.
bridge in Edinburgh
A bridge in Edinburgh is a structural crossing—often historic or architecturally distinctive—that spans natural or urban obstacles within the city, facilitating the movement of people, vehicles, or rail.
-
E.
bridge in Bristol
A bridge in Bristol is a structural crossing—such as the iconic Clifton Suspension Bridge—spanning a river, road, or gorge within or near the city to connect different areas and support transport and movement.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.