Triple
T30189512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCP3-PD |
E767433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | climate change scenario |
C25371
|
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: climate change scenario Context triple: [RCP3-PD, instanceOf, climate change scenario]
-
A.
climate change scenario family
chosen
A climate change scenario family is a structured set of related future climate projections that share common assumptions about socio-economic development, emissions pathways, and policy choices to explore a range of possible climate outcomes.
-
B.
climate phenomenon
A climate phenomenon is a recurring or notable pattern or event in the Earth’s climate system, such as El Niño or monsoon cycles, that significantly influences weather and environmental conditions over large regions and timescales.
-
C.
climate model
A climate model is a computational representation of the Earth’s climate system that simulates interactions among the atmosphere, oceans, land surface, and ice to project past, present, and future climate conditions.
-
D.
climate change book
A climate change book is a written work that explains the causes, impacts, and potential solutions to global climate change, often combining scientific evidence with policy, economic, and social perspectives.
-
E.
climate system
The climate system is the interconnected set of components—including the atmosphere, oceans, land surface, cryosphere, and biosphere—that together determine Earth’s long-term weather patterns and energy balance.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:28 p.m.