Triple
T17368358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 664 |
E422242
|
entity |
| Predicate | bridgeTunnelRole |
P127217
|
FINISHED |
| Object | major crossing of Hampton Roads separate from the Hampton Roads Bridge–Tunnel |
—
|
LITERAL FINISHED |
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: major crossing of Hampton Roads separate from the Hampton Roads Bridge–Tunnel | Statement: [Interstate 664, bridgeTunnelRole, major crossing of Hampton Roads separate from the Hampton Roads Bridge–Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeTunnelRole Context triple: [Interstate 664, bridgeTunnelRole, major crossing of Hampton Roads separate from the Hampton Roads Bridge–Tunnel]
-
A.
hasBridgeTunnel
Indicates that there exists a bridge or tunnel connection between two locations or structures.
-
B.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
C.
tollBridge
Indicates that passage across a bridge requires payment of a toll or fee.
-
D.
bridgeAndTunnelRatio
Indicates the proportion between the number or extent of bridges and tunnels within a given system, network, or area.
-
E.
bridgeName
Indicates the designated name assigned to a specific bridge.
- F. None of above. chosen
Provenance (4 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6790448190a24047523a019f81 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.