Triple
T1544992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clean Trucks Program |
E32957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air quality program |
C2060
|
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: air quality program Context triple: [Clean Trucks Program, instanceOf, air quality program]
-
A.
air quality permitting program
An air quality permitting program is a regulatory framework that evaluates, authorizes, and monitors facilities’ air emissions to ensure compliance with air pollution control standards and protect public health and the environment.
-
B.
air quality management plan
An air quality management plan is a structured framework of policies, strategies, and actions designed to monitor, control, and improve air quality to meet health and environmental standards.
-
C.
environmental programme
chosen
An environmental programme is an organized set of coordinated activities, policies, and initiatives designed to protect, manage, or improve the natural environment and promote sustainable practices.
-
D.
airline cleanliness program
An airline cleanliness program is a systematic set of policies, procedures, and standards designed to ensure aircraft cabins, restrooms, and common areas are regularly cleaned, sanitized, and maintained to protect passenger health and enhance comfort.
-
E.
environmental health risk assessment program
An environmental health risk assessment program systematically evaluates potential adverse health effects from environmental hazards by analyzing exposure, toxicity, and population vulnerability to inform risk management decisions.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.