Triple
T29896289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipping Efficiency initiative |
E759287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carbon War Room program |
C27048
|
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: Carbon War Room program Context triple: [Shipping Efficiency initiative, instanceOf, Carbon War Room program]
-
A.
climate protection program
chosen
A climate protection program is an organized set of policies, actions, and measures designed to reduce greenhouse gas emissions, enhance climate resilience, and promote sustainable environmental practices.
-
B.
World Resources Institute program
A World Resources Institute program is an organized initiative that applies research, partnerships, and policy tools to advance sustainable management of the world’s environmental and natural resources.
-
C.
United States climate pledge
The United States climate pledge is a national commitment outlining specific targets and actions to reduce greenhouse gas emissions, enhance climate resilience, and support global efforts to limit climate change.
-
D.
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.
-
E.
climate policy research program
A climate policy research program systematically investigates, analyzes, and evaluates policies and strategies aimed at mitigating and adapting to climate change to inform evidence-based decision-making.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:04 p.m.