Triple
T35477695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 13 in Virginia |
E1025379
|
entity |
| Predicate | bridgeTunnelComponent |
P123927
|
FINISHED |
| Object | Chesapeake Bay Bridge–Tunnel causeways |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Chesapeake Bay Bridge–Tunnel causeways | Statement: [U.S. Route 13 in Virginia, bridgeTunnelComponent, Chesapeake Bay Bridge–Tunnel causeways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeTunnelComponent Context triple: [U.S. Route 13 in Virginia, bridgeTunnelComponent, Chesapeake Bay Bridge–Tunnel causeways]
-
A.
hasBridgeTunnel
Indicates that there exists a bridge or tunnel connection between two locations or structures.
-
B.
bridgeTunnelRole
Indicates a functional role that an entity plays specifically in relation to a bridge or tunnel, such as operating, managing, or maintaining it.
-
C.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
D.
hasBridgeAndTunnelStructures
chosen
Indicates that there exist both bridge and tunnel structures associated with or connecting the related entities.
-
E.
bridgeStructure
Indicates a structural relationship where one entity functions as a bridge that spans or connects two separate points or areas.
- F. None of above.
Provenance (3 batches)
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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.