Triple
T9072135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairview Container Terminal |
E217393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intermodal freight terminal |
C5917
|
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 freight terminal Context triple: [Fairview Container Terminal, instanceOf, intermodal freight terminal]
-
A.
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.
-
B.
inland port
chosen
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.
ferry terminal
A ferry terminal is a designated facility where passengers and vehicles embark and disembark from ferries, typically providing ticketing, waiting areas, and docking infrastructure.
-
D.
ground transportation facility
A ground transportation facility is a designated location that supports the movement, transfer, and management of passengers or goods via land-based modes such as buses, trains, cars, or trucks.
-
E.
group of passenger rail terminals
A group of passenger rail terminals is a collection of interconnected or related railway stations designed for boarding, alighting, and transferring passengers within a coordinated transport network.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:12 p.m.