Triple
T1851645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention on Facilitation of International Maritime Traffic |
E41607
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime convention |
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 convention Context triple: [Convention on Facilitation of International Maritime Traffic, instanceOf, maritime convention]
-
A.
maritime confederation
A maritime confederation is a loose alliance of seafaring states or cities that cooperate to control trade routes, naval defense, and maritime law while retaining their political independence.
-
B.
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.
-
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 reference work
A maritime reference work is a comprehensive resource that compiles and organizes authoritative information about ships, navigation, seafaring practices, maritime law, and ocean-related subjects for quick consultation.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:33 p.m.