Triple
T8629340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Convention on Maritime Radio Communications |
E204360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime safety instrument |
C3137
|
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 instrument Context triple: [International Convention on Maritime Radio Communications, instanceOf, maritime safety instrument]
-
A.
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.
-
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.
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.
-
D.
International Maritime Organization instrument
chosen
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.
-
E.
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.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.