Triple
T16830842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corporate Average Fuel Economy program |
E409143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fuel economy regulation |
C19622
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: fuel economy regulation Context triple: [Corporate Average Fuel Economy program, instanceOf, fuel economy regulation]
-
A.
fuel rationing program
A fuel rationing program is a system that allocates limited fuel supplies among users or sectors according to predefined rules and priorities to manage scarcity and ensure essential needs are met.
-
B.
economic regulation
chosen
Economic regulation is the set of laws, rules, and administrative actions through which governments influence, control, or guide economic activity, markets, and business behavior to achieve public policy objectives.
-
C.
New Car Assessment Program
A New Car Assessment Program is a vehicle safety rating system that evaluates and compares the crashworthiness and safety performance of new car models using standardized tests and criteria.
-
D.
vehicle scrappage program
A vehicle scrappage program is a policy initiative that offers incentives to retire older, less efficient vehicles and replace them with newer, cleaner models to reduce emissions and improve road safety.
-
E.
internal combustion engine vehicle
An internal combustion engine vehicle is a motorized transport device that converts the chemical energy of fuel into mechanical work through controlled combustion within an engine to drive its wheels or propulsion system.
- F. None of above.
Provenance (1 batch)
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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:23 a.m.