Triple
T15666018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mining Code for activities in the Area |
E377189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law of the sea instrument |
C35685
|
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: law of the sea instrument Context triple: [Mining Code for activities in the Area, instanceOf, law of the sea instrument]
-
A.
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.
-
B.
law of the sea case
A law of the sea case is a legal dispute or judicial proceeding concerning the interpretation, application, or enforcement of international rules governing maritime zones, navigation rights, resource exploitation, and ocean governance.
-
C.
naval legislation
Naval legislation comprises the body of laws, regulations, and international agreements that govern the operation, safety, security, and environmental impact of ships and maritime activities at sea and in ports.
-
D.
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.
-
E.
maritime polity
A maritime polity is a political entity whose power, economy, and cultural identity are fundamentally organized around control of the sea, seafaring, and maritime trade routes.
- F. None of above. chosen
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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:16 a.m.