Triple
T14596588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euro 6 |
E342583
|
entity |
| Predicate | setsLimitFor |
P9530
|
FINISHED |
| Object | NOx emissions from diesel passenger cars |
—
|
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 from diesel passenger cars | Statement: [Euro 6, setsLimitFor, NOx emissions from diesel passenger cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsLimitFor Context triple: [Euro 6, setsLimitFor, NOx emissions from diesel passenger cars]
-
A.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
B.
setsMaximum
chosen
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
-
C.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
D.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
hasLimitSet
Indicates that there is a defined boundary, range, or constraint applied to 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43581348190b5362251c3a89654 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.