Triple
T1967978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safety Management Certificate |
E42732
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime safety certificate |
C11964
|
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 certificate Context triple: [Safety Management Certificate, instanceOf, maritime safety certificate]
-
A.
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.
-
B.
maritime navigation authority
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.
-
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 incident
A maritime incident is any unexpected or unintended event involving a vessel or marine operation that compromises or threatens safety, the environment, property, or normal navigation at sea or in navigable waters.
-
E.
maritime livery marking
A maritime livery marking is a distinctive visual design or emblem applied to ships and related assets to identify ownership, affiliation, or brand identity within a nautical context.
- F. None of above. chosen
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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.