Triple
T34648595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewisville Lake Toll Bridge |
E889771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Texas |
C61638
|
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 Texas Context triple: [Lewisville Lake Toll Bridge, instanceOf, bridge in Texas]
-
A.
bridge in Dallas, Texas
A bridge in Dallas, Texas is a structural crossing—often spanning rivers, highways, or railways—designed to support vehicular, pedestrian, or rail traffic while integrating with the city’s transportation network and urban landscape.
-
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 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 Kentucky
A bridge in Kentucky is a structural crossing—such as a roadway, railway, or pedestrian span—located within the state of Kentucky that connects two points separated by a physical obstacle like a river, valley, or roadway.
-
E.
bridge in Brazil
A bridge in Brazil is a structural construction that spans physical obstacles such as rivers, valleys, or roads within Brazilian territory, facilitating transportation and connectivity while reflecting local engineering practices and environmental 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.