Triple
T12791729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Miami River terminals |
E305782
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cargo terminal network |
C28493
|
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: cargo terminal network Context triple: [Port of Miami River terminals, instanceOf, cargo terminal network]
-
A.
cargo-passenger terminal
A cargo-passenger terminal is a facility designed to handle both freight operations and passenger services, integrating logistics, customs, and boarding processes within a single transportation hub.
-
B.
container terminal complex
A container terminal complex is a large, integrated facility where containerized cargo is transferred between ships, trucks, and trains, supported by specialized infrastructure, equipment, and logistics services.
-
C.
maritime cargo terminal
chosen
A maritime cargo terminal is a specialized facility at a seaport where ships are loaded and unloaded, and cargo is temporarily stored, sorted, and transferred between sea and land transportation modes.
-
D.
bulk cargo terminal
A bulk cargo terminal is a specialized port facility designed for the efficient handling, storage, and transfer of unpackaged bulk commodities such as coal, grain, ore, and fertilizers between ships, land transport, and storage areas.
-
E.
cargo airport
A cargo airport is a specialized aviation facility designed primarily for the handling, storage, and transportation of freight and mail, featuring extensive logistics infrastructure and limited or no passenger services.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:30 p.m.