Triple
T9169715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Document of Compliance |
E220051
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international maritime document |
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: international maritime document Context triple: [Document of Compliance, instanceOf, international maritime document]
-
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.
international diplomatic document
An international diplomatic document is a formal written instrument exchanged between states or international organizations to record, communicate, or formalize agreements, positions, or understandings in the conduct of foreign relations.
-
C.
international port
An international port is a major maritime facility equipped to handle the arrival, departure, and transfer of cargo and passengers between countries, integrating customs, logistics, and transportation infrastructure.
-
D.
maritime passage
A maritime passage is a navigable sea route or waterway that connects larger bodies of water, enabling the movement of ships and maritime traffic between regions.
-
E.
maritime industry
The maritime industry encompasses the global network of activities, services, and infrastructure involved in the design, construction, operation, and regulation of ships and marine transport for cargo, passengers, and offshore resources.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:22 p.m.