Triple
T23457797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAPS (Twin Annular Pre-mixing Swirler) |
E567979
|
entity |
| Predicate | targetsEmission |
P29039
|
FINISHED |
| Object | nitrogen oxides (NOx) |
—
|
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: nitrogen oxides (NOx) | Statement: [TAPS (Twin Annular Pre-mixing Swirler), targetsEmission, nitrogen oxides (NOx)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsEmission Context triple: [TAPS (Twin Annular Pre-mixing Swirler), targetsEmission, nitrogen oxides (NOx)]
-
A.
emissionStandardTarget
Indicates the specific emissions limit or performance level that something is intended or required to meet.
-
B.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
targetsEcosystem
Indicates that an action, product, or policy is directed toward, affects, or is specifically intended for a particular ecosystem.
-
D.
targetPollutant
chosen
Indicates that something is the specific pollutant that is being aimed at, affected, or addressed by an action, process, or regulation.
-
E.
emissionType
Indicates the specific category or kind of emission associated with an entity or activity.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a69904588190b44c84021e94ae63 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.