Triple
T10203234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor Bridge (pedestrian and cycle) |
E238936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road bridge converted to pedestrian use |
C3860
|
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: road bridge converted to pedestrian use Context triple: [Windsor Bridge (pedestrian and cycle), instanceOf, road bridge converted to pedestrian use]
-
A.
pedestrian bridge
chosen
A pedestrian bridge is a raised structure designed exclusively for people on foot (and often cyclists) to safely cross obstacles such as roads, railways, or waterways without interacting with vehicular traffic.
-
B.
pedestrian skybridge
A pedestrian skybridge is an elevated, enclosed or open walkway that connects two or more buildings above ground level, allowing people to cross safely and conveniently without interacting with street traffic.
-
C.
former bridge
A former bridge is a structure that once functioned as a crossing over an obstacle such as water, a road, or a valley, but has since been decommissioned, repurposed, or rendered unusable for its original bridging purpose.
-
D.
ornamental bridge
An ornamental bridge is a decorative structure, often smaller in scale than functional bridges, designed primarily to enhance the aesthetic appeal of a landscape or garden while sometimes providing light pedestrian passage.
-
E.
pedestrian walkway
A pedestrian walkway is a designated path or corridor intended exclusively or primarily for people traveling on foot, providing safe and convenient passage separated from vehicular traffic.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:14 p.m.