Triple
T7065084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PortMiami Tunnel |
E164325
|
entity |
| Predicate | reducesTrafficOn |
P32500
|
FINISHED |
| Object | downtown Miami surface streets |
—
|
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: downtown Miami surface streets | Statement: [PortMiami Tunnel, reducesTrafficOn, downtown Miami surface streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducesTrafficOn Context triple: [PortMiami Tunnel, reducesTrafficOn, downtown Miami surface streets]
-
A.
relievesTrafficFrom
chosen
Indicates that one entity reduces or alleviates traffic congestion that would otherwise occur on another entity.
-
B.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
C.
trafficRestriction
Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
-
D.
canReduceSpeedTo
Indicates that an entity has the capability to lower its speed to a specified level or threshold.
-
E.
facilitatesTrafficFlowBetween
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:39 p.m.