Triple
T10952125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 5 Ship Canal Bridge |
E258749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Seattle |
C28614
|
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 Seattle Context triple: [Interstate 5 Ship Canal Bridge, instanceOf, bridge in Seattle]
-
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.
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.
-
C.
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.
-
D.
bridge in London
A bridge in London is a structural crossing over the River Thames or other waterways in the city, designed to support vehicular, rail, or pedestrian traffic while integrating with the historic and urban landscape.
-
E.
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.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:23 p.m.