Triple
T10835259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Part E – Exemptions |
E255738
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of an international maritime regulation |
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: section of an international maritime regulation Context triple: [Part E – Exemptions, instanceOf, section of an international maritime regulation]
-
A.
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.
-
B.
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.
-
C.
chapter of an international treaty
A chapter of an international treaty is a major structural division that groups together related articles and provisions addressing a specific thematic area or subject matter within the overall agreement.
-
D.
section of ship
A section of ship is a distinct structural subdivision of a vessel, such as the bow, midship, or stern, designed to house specific functions, equipment, or accommodations.
-
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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.