Triple
T1544993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clean Trucks Program |
E32957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | port emissions reduction program |
C5436
|
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: port emissions reduction program Context triple: [Clean Trucks Program, instanceOf, port emissions reduction program]
-
A.
port emissions reduction initiative
chosen
A port emissions reduction initiative is a coordinated program of policies, technologies, and operational changes designed to lower air pollutants and greenhouse gas emissions from maritime, terminal, and landside activities within and around a port.
-
B.
cap-and-trade program
A cap-and-trade program is a regulatory system that sets an overall limit on emissions and allows entities to buy and sell emission allowances, creating a market incentive to reduce pollution at the lowest cost.
-
C.
seaport
A seaport is a coastal facility equipped with harbors, docks, and infrastructure to enable the loading, unloading, storage, and transfer of cargo and passengers between sea and land transportation.
-
D.
water pollution control program
A water pollution control program is an organized set of policies, regulations, monitoring activities, and treatment measures designed to prevent, reduce, and manage contaminants entering water bodies to protect human health and aquatic ecosystems.
-
E.
port authority
A port authority is an organization responsible for managing, regulating, and developing a seaport or group of ports, including their infrastructure, operations, and related maritime activities.
- 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.