Triple
T1967980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safety Management Certificate |
E42732
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ISM Code certificate |
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: ISM Code certificate Context triple: [Safety Management Certificate, instanceOf, ISM Code certificate]
-
A.
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.
-
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.
interoperability certification
Interoperability certification is a formal validation process that confirms different systems, products, or services can reliably exchange and use information according to defined standards and protocols.
-
D.
ISO standard code set
A standardized collection of internationally recognized codes defined by the International Organization for Standardization (ISO) to uniquely and consistently represent specific types of data, such as countries, currencies, languages, or measurements.
-
E.
Market Identifier Code
A Market Identifier Code (MIC) is a standardized four-character code used to uniquely identify securities trading venues such as exchanges, trading platforms, and markets worldwide.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.