Triple
T9734479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitrogen Oxide Emission Control Areas |
E236022
|
entity |
| Predicate | usesControlMeasures |
P49579
|
FINISHED |
| Object | selective catalytic reduction |
—
|
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: selective catalytic reduction | Statement: [Nitrogen Oxide Emission Control Areas, usesControlMeasures, selective catalytic reduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesControlMeasures Context triple: [Nitrogen Oxide Emission Control Areas, usesControlMeasures, selective catalytic reduction]
-
A.
controlMeasure
Indicates a relationship where one entity implements or applies a method, action, or mechanism to regulate, mitigate, or manage a risk, process, or condition associated with another entity.
-
B.
measuresSafetyUsing
Indicates that an entity evaluates or assesses safety by employing a specified method, tool, or standard.
-
C.
usedToControl
chosen
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
D.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over another entity or process.
-
E.
protectionMeasures
Indicates actions or safeguards implemented to prevent harm, damage, or risk to someone or something.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eebcec08190a9d4606fd26f2e19 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.