Triple
T34206101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FuelEU Maritime initiative |
E877514
|
entity |
| Predicate | coversEmissionsFrom |
P170290
|
FINISHED |
| Object | CO2 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: CO2 | Statement: [FuelEU Maritime initiative, coversEmissionsFrom, CO2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversEmissionsFrom Context triple: [FuelEU Maritime initiative, coversEmissionsFrom, CO2]
-
A.
emissionsCoverage
chosen
Indicates the extent to which emissions from a given source or activity are included within a specified accounting, reporting, or regulatory boundary.
-
B.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
C.
coversTo
Indicates that one entity extends its coverage or protective scope to include another entity.
-
D.
pollutantsCovered
Indicates that certain pollutants are included within the scope, protection, regulation, or consideration defined by a particular entity, policy, or agreement.
-
E.
cobertura
Indicates that one entity provides coverage, protection, or a covering layer over another entity.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:55 a.m.