Triple
T28401450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMO Instruments Implementation Code |
E719403
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IMO code |
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: IMO code Context triple: [IMO Instruments Implementation Code, instanceOf, IMO code]
-
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 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.
-
C.
maritime mobile service identity
A maritime mobile service identity (MMSI) is a unique nine-digit number assigned to a ship, coast station, or other maritime radio station to identify it in digital communications and safety systems.
-
D.
UN/LOCODE identifier
A UN/LOCODE identifier is a standardized five-character code assigned by the United Nations to uniquely identify locations such as ports, cities, and transport hubs used in international trade and logistics.
-
E.
maritime classification society
A maritime classification society is an independent organization that establishes and verifies technical standards for the design, construction, and maintenance of ships and offshore structures to ensure their safety and seaworthiness.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:20 a.m.