Triple
T30142709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen emissions scandal |
E766169
|
entity |
| Predicate | affectedEngineFamily |
P131232
|
FINISHED |
| Object | EA189 diesel engines |
—
|
NE NERFINISHED |
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: EA189 diesel engines | Statement: [Volkswagen emissions scandal, affectedEngineFamily, EA189 diesel engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedEngineFamily Context triple: [Volkswagen emissions scandal, affectedEngineFamily, EA189 diesel engines]
-
A.
belongsToEngineFamily
Indicates that an engine is a member of, or classified under, a specific engine family or series.
-
B.
notableEngineFamily
Indicates that one entity is a well-known or significant engine family associated with the other entity.
-
C.
successorEngineFamily
Indicates that one engine family directly follows and replaces another in a product or development lineage.
-
D.
associatedWithEngine
chosen
Indicates a relationship in which something is connected, linked, or related to an engine, typically through use, function, or dependency.
-
E.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 7:18 p.m.