Triple
T22468789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Street Bridge |
E555432
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Philadelphia |
C46353
|
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 Philadelphia Context triple: [South Street Bridge, instanceOf, bridge in Philadelphia]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
river bridge
A river bridge is a structure built to span a river, providing a stable pathway for vehicles, pedestrians, or rail traffic to cross from one bank to the other.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:48 p.m.