Triple
T34206081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FuelEU Maritime initiative |
E877514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime decarbonisation policy |
C49051
|
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 decarbonisation policy Context triple: [FuelEU Maritime initiative, instanceOf, maritime decarbonisation policy]
-
A.
port emissions reduction initiative
A port emissions reduction initiative is a coordinated program of policies, technologies, and operational changes designed to lower air pollutants and greenhouse gas emissions from maritime, terminal, and landside activities within and around a port.
-
B.
marine pollution control regime
A marine pollution control regime is an integrated set of laws, institutions, policies, and enforcement mechanisms designed to prevent, reduce, and manage pollution in marine environments from various human activities.
-
C.
maritime industry
The maritime industry encompasses the global network of activities, services, and infrastructure involved in the design, construction, operation, and regulation of ships and marine transport for cargo, passengers, and offshore resources.
-
D.
marine policy framework
chosen
A marine policy framework is a structured set of principles, regulations, and governance mechanisms that guide the sustainable use, management, and protection of ocean and coastal resources.
-
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.
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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:55 a.m.