Triple
T23734688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broad Street Bridge (Columbus, Ohio) |
E586508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Columbus, Ohio |
C47997
|
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 Columbus, Ohio Context triple: [Broad Street Bridge (Columbus, Ohio), instanceOf, bridge in Columbus, Ohio]
-
A.
bridge in Philadelphia
A bridge in Philadelphia is a large, engineered structure spanning a physical obstacle such as the Schuylkill or Delaware River within the Philadelphia area, enabling the safe and efficient movement of vehicles, pedestrians, or trains.
-
B.
bridge in New York City
A bridge in New York City is a large-scale transportation structure spanning waterways or land to connect boroughs and neighborhoods, supporting vehicular, rail, bicycle, and pedestrian traffic within the city’s dense urban environment.
-
C.
Hudson River bridge
A Hudson River bridge is a large transportation structure spanning the Hudson River to connect communities and facilitate the movement of vehicles, trains, pedestrians, or utilities between its banks.
-
D.
bridge in Miami
A bridge in Miami is a structural crossing, often spanning waterways or highways, designed to support vehicular, pedestrian, or rail traffic while withstanding the region’s coastal climate and environmental conditions.
-
E.
bridge in Seattle
A bridge in Seattle is a structural crossing—often spanning water or valleys—that connects different parts of the city or region, accommodating vehicles, pedestrians, and sometimes rail while withstanding the Pacific Northwest’s climate and seismic conditions.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:10 p.m.