Triple
T4718786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton Roads Bridge–Tunnel |
E104711
|
entity |
| Predicate | expansionGoal |
P38715
|
FINISHED |
| Object | increase capacity and reduce congestion |
—
|
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: increase capacity and reduce congestion | Statement: [Hampton Roads Bridge–Tunnel, expansionGoal, increase capacity and reduce congestion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionGoal Context triple: [Hampton Roads Bridge–Tunnel, expansionGoal, increase capacity and reduce congestion]
-
A.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
B.
expansionProject
Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
-
C.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
D.
plannedExpansion
Indicates that an entity has a scheduled or intended increase in size, capacity, scope, or presence in the future.
-
E.
expansionReason
chosen
Indicates the reason or cause behind an expansion event or process occurring between entities.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.