Triple
T12032727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STCW Parties |
E286451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime convention parties |
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 parties Context triple: [STCW Parties, instanceOf, maritime convention parties]
-
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.
law of the sea institution
A law of the sea institution is an organization or body responsible for developing, interpreting, implementing, or enforcing legal rules and frameworks governing the use, management, and protection of the world’s oceans and marine resources.
-
C.
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.
-
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.
international legal body roster
A curated list of qualified legal professionals and institutions recognized and authorized to participate in proceedings, advisory roles, or decision-making within international legal bodies.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.