Triple
T34166367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Coast Guard Station Sandy Hook |
E876423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime safety facility |
C47198
|
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 safety facility Context triple: [U.S. Coast Guard Station Sandy Hook, instanceOf, maritime safety facility]
-
A.
maritime support facility
chosen
A maritime support facility is a shore-based installation that provides logistical, maintenance, operational, and emergency services to vessels and maritime operations.
-
B.
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.
-
C.
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.
-
D.
maritime safety regulation
Maritime safety regulation is the body of laws, standards, and procedures designed to prevent accidents, protect life, property, and the marine environment, and ensure safe operations in maritime activities.
-
E.
maritime rescue device
A maritime rescue device is equipment specifically designed to aid in locating, supporting, and safely recovering people in distress at sea or other navigable waters.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:54 a.m.