Triple
T9486321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMO codes and guidelines on noxious liquid substances |
E228770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime safety standard |
C23670
|
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 standard Context triple: [IMO codes and guidelines on noxious liquid substances, instanceOf, maritime safety standard]
-
A.
maritime safety regulation
chosen
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 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.
-
D.
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.
-
E.
maritime security procedure
A maritime security procedure is a standardized set of measures and protocols designed to prevent, detect, and respond to threats or unlawful acts against ships, ports, and offshore facilities.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:55 p.m.