Triple
T21317983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuller Warren Bridge |
E525528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge over the St. Johns River |
C22181
|
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 over the St. Johns River Context triple: [Fuller Warren Bridge, instanceOf, bridge over the St. Johns River]
-
A.
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.
-
B.
river bridge
chosen
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.
Jacksonville Skyway station
A Jacksonville Skyway station is an elevated or ground-level transit facility along Jacksonville's automated people mover system where passengers board, alight, and transfer between Skyway trains and other transportation modes.
-
D.
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.
-
E.
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.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:36 p.m.