Triple
T26034154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOx SIP Call |
E647507
|
entity |
| Predicate | complianceInstrument |
P163708
|
FINISHED |
| Object | NOx emissions allowances |
—
|
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: NOx emissions allowances | Statement: [NOx SIP Call, complianceInstrument, NOx emissions allowances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complianceInstrument Context triple: [NOx SIP Call, complianceInstrument, NOx emissions allowances]
-
A.
complianceInstrument
chosen
Indicates that one entity serves as a tool, mechanism, or measure used to ensure, demonstrate, or enforce compliance with a rule, standard, or obligation for another entity.
-
B.
providesCompliance
Indicates that one entity supplies or ensures adherence to required rules, standards, or regulations for another entity.
-
C.
indicatesComplianceWith
Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
-
D.
complianceUse
Indicates that something is used, implemented, or behaves in accordance with a specified rule, standard, or compliance requirement.
-
E.
regulatesComplianceWith
Indicates that one entity oversees, enforces, or sets rules to ensure another entity adheres to specified standards, laws, or requirements.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 22, 2026, 9:06 a.m.