Triple
T37350467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Lawrence River ports |
E927307
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime facility system |
C53972
|
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 facility system Context triple: [St. Lawrence River ports, instanceOf, maritime facility system]
-
A.
maritime support facility
A maritime support facility is a shore-based installation that provides logistical, maintenance, operational, and emergency services to vessels and maritime operations.
-
B.
maritime structure
A maritime structure is a man-made construction located in or near bodies of water, designed to support marine activities such as navigation, transportation, resource extraction, or coastal protection.
-
C.
maritime security infrastructure
Maritime security infrastructure encompasses the integrated systems, facilities, technologies, and organizational frameworks designed to protect maritime domains, ports, and shipping routes from threats, ensure safe navigation, and support law enforcement and emergency response at sea.
-
D.
port facility complex
chosen
A port facility complex is an integrated area of land and water with infrastructure, equipment, and services designed to support the berthing, loading, unloading, storage, and transfer of cargo and passengers between sea and land transport modes.
-
E.
docking facility
A docking facility is a designated structure or area where vehicles, vessels, or spacecraft securely attach for loading, unloading, maintenance, or passenger transfer.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.