Triple
T6110310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Intermodal Center |
E136220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intermodal transportation center |
C82
|
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: intermodal transportation center Context triple: [Miami Intermodal Center, instanceOf, intermodal transportation center]
-
A.
transport hub
chosen
A transport hub is a central location where multiple modes or routes of transportation intersect, enabling the efficient transfer of passengers or goods between them.
-
B.
combined civic building and transportation hub
A combined civic building and transportation hub is a multifunctional public facility that integrates government or community services with major transit infrastructure to centralize access, improve connectivity, and enhance urban efficiency.
-
C.
cross-border terminal
A cross-border terminal is a transportation facility located at or near an international boundary that consolidates, processes, and transfers passengers or freight between different countries’ transport networks while handling customs, immigration, and regulatory controls.
-
D.
rapid transit depot
A rapid transit depot is a specialized facility where urban rail vehicles are stored, inspected, maintained, and dispatched for service on a rapid transit network.
-
E.
railway–metro interchange
A railway–metro interchange is a transport facility where mainline railway services and urban metro lines connect, enabling passengers to transfer conveniently between regional and local rail networks.
- F. None of above.
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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:13 p.m.