Triple
T9734412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulfur Emission Control Areas |
E236021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime environmental regulation zone |
C2575
|
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 environmental regulation zone Context triple: [Sulfur Emission Control Areas, instanceOf, maritime environmental regulation zone]
-
A.
maritime zone
chosen
A maritime zone is a legally defined area of the sea, measured from a coastal state's baseline, within which specific rights, jurisdiction, and responsibilities are allocated under international law.
-
B.
marine conservation area
A marine conservation area is a designated ocean or coastal region managed to protect marine ecosystems, species, and natural resources from harmful human activities while allowing compatible, sustainable use.
-
C.
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.
-
D.
maritime jurisdictional office
A maritime jurisdictional office is a governmental or regulatory entity responsible for overseeing, enforcing, and administering laws, regulations, and policies within a defined maritime area or coastal zone.
-
E.
marine ecoregion
A marine ecoregion is a geographically distinct area of ocean or coastal waters characterized by a relatively homogeneous community of species, environmental conditions, and ecological processes.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:22 p.m.