Triple
T20903394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NW 5th Street Bridge |
E514728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Miami |
C43909
|
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 Miami Context triple: [NW 5th Street Bridge, instanceOf, bridge in Miami]
-
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.
bridge in California
A bridge in California is a man-made structure that spans physical obstacles such as water, valleys, or roads within the state of California to provide transportation routes for vehicles, pedestrians, or rail.
-
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 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.
bridge in Dubai
A bridge in Dubai is a structural crossing designed to span physical obstacles such as water or roads within the city, integrating modern engineering with the emirate’s distinctive architectural and urban landscape.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:47 p.m.