Triple
T17423476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPI F40PH-3C |
E423675
|
entity |
| Predicate | hasEmissionControl |
P17326
|
FINISHED |
| Object | upgraded exhaust system |
—
|
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: upgraded exhaust system | Statement: [MPI F40PH-3C, hasEmissionControl, upgraded exhaust system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmissionControl Context triple: [MPI F40PH-3C, hasEmissionControl, upgraded exhaust system]
-
A.
emissionsControl
chosen
Indicates a relationship where one entity regulates, limits, or manages the release of emissions produced by another entity or process.
-
B.
emissionsStandardIssue
Indicates that an entity has been issued or is subject to a specific emissions standard or regulatory requirement for allowable emissions.
-
C.
hasPersistentGasEmissions
Indicates that an entity continuously or repeatedly releases gaseous substances over an extended period.
-
D.
emissionType
Indicates the specific category or kind of emission associated with an entity or activity.
-
E.
emissionCharacteristic
Indicates a relationship where an entity is associated with a specific property or quality of its emissions (such as type, level, or pattern of emission).
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44238b418819095c6a013d3ff3b17 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.