Triple
T27805750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaii state harbor system |
E702371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | port and harbor network |
C12386
|
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: port and harbor network Context triple: [Hawaii state harbor system, instanceOf, port and harbor network]
-
A.
naval anchorage network
A naval anchorage network is an interconnected system of designated maritime anchor points, supporting infrastructure, and communication links that enables coordinated deployment, resupply, and protection of naval vessels across strategic sea areas.
-
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.
seaport
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.
-
D.
port area
chosen
A port area is a designated coastal or riverside zone equipped with infrastructure and facilities for the berthing, loading, unloading, storage, and transfer of cargo and passengers between land and water transport.
-
E.
harbormaster office
A harbormaster office is the administrative and operational center at a port or marina responsible for coordinating vessel movements, enforcing harbor regulations, and managing maritime safety and 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:38 p.m.