Triple
T3371012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maritime Authority System |
E70953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime safety authority |
C4267
|
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 authority Context triple: [Maritime Authority System, instanceOf, maritime safety authority]
-
A.
maritime navigation authority
chosen
A maritime navigation authority is an organization responsible for regulating, managing, and ensuring the safety and efficiency of vessel movements and navigational systems within designated waters.
-
B.
maritime safety certificate
A maritime safety certificate is an official document issued by a competent authority confirming that a vessel complies with required safety regulations and standards for operation at sea.
-
C.
International Maritime Organization instrument
An International Maritime Organization instrument is a formal legal or regulatory document—such as a convention, code, or guideline—adopted by the IMO to establish international standards for maritime safety, security, and environmental protection.
-
D.
maritime security code
A maritime security code is a set of international or national regulations and standards designed to prevent, detect, and respond to security threats against ships, ports, and maritime infrastructure.
-
E.
public safety agency
A public safety agency is an organization responsible for protecting the public from threats and hazards by preventing, responding to, and managing emergencies, crimes, and disasters within a community or jurisdiction.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:13 p.m.