Triple
T33863074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILO Maritime Labour Convention |
E867972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime labour instrument |
C6139
|
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 labour instrument Context triple: [ILO Maritime Labour Convention, instanceOf, maritime labour instrument]
-
A.
International Maritime Organization instrument
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 workforce
The maritime workforce comprises all personnel engaged in seafaring, port operations, and related marine industries who ensure the safe, efficient, and sustainable movement of goods and people across waterways.
-
C.
ILO instrument
chosen
An ILO instrument is a formal legal document—such as a convention, recommendation, or protocol—adopted by the International Labour Organization to set international labor standards and guide member states’ labor policies and practices.
-
D.
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.
-
E.
maritime safety certificate
A maritime safety certificate is an official document issued by a competent authority confirming that a vessel complies with required safety regulations and standards for operation at sea.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.