Triple
T25010748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Florida seaport system |
E625977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional seaport system |
C452
|
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: regional seaport system Context triple: [South Florida seaport system, instanceOf, regional seaport system]
-
A.
seaport
chosen
A seaport is a coastal facility equipped with harbors, docks, and infrastructure to enable the loading, unloading, storage, and transfer of cargo and passengers between sea and land transportation.
-
B.
inland port
An inland port is a logistics and transportation hub located away from coastal seaports, typically along rivers, canals, or rail corridors, that facilitates the transfer, storage, and distribution of goods between different modes of transport.
-
C.
Arctic port
An Arctic port is a maritime facility located within or near the Arctic Circle that supports the docking, loading, unloading, and servicing of vessels operating in polar conditions, often adapted for ice navigation and extreme weather.
-
D.
maritime convoy system
A maritime convoy system is an organized method of grouping merchant or military vessels to sail together under coordinated protection and navigation to reduce risks from threats such as enemy attacks, piracy, or hazardous conditions.
-
E.
maritime convoy system
A maritime convoy system is an organized method of grouping and coordinating multiple ships under shared routing, scheduling, and protection protocols to enhance safety, security, and efficiency during sea transit.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:05 a.m.