Triple
T20365065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa maritime transportation network |
E496886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime transportation network |
C4130
|
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: maritime transportation network Context triple: [Tampa maritime transportation network, instanceOf, maritime transportation network]
-
A.
transoceanic trade network
A transoceanic trade network is a system of interconnected maritime routes, ports, merchants, and institutions that facilitate the large-scale exchange of goods, people, capital, and ideas across oceans between distant regions of the world.
-
B.
ferry service network
A ferry service network is a coordinated system of water-based transport routes, vessels, terminals, and schedules that moves passengers and cargo between multiple ports or coastal locations.
-
C.
maritime passage
A maritime passage is a navigable sea route or waterway that connects larger bodies of water, enabling the movement of ships and maritime traffic between regions.
-
D.
marine transit service
A marine transit service is an organized operation that transports passengers and/or cargo over water using vessels such as ferries, ships, or boats along scheduled or on-demand routes.
-
E.
transport infrastructure network
chosen
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:26 a.m.