Triple
T4079130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 8.2 kiloyear event |
E87434
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | abrupt climate change event |
C3904
|
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: abrupt climate change event Context triple: [8.2 kiloyear event, instanceOf, abrupt climate change event]
-
A.
climate phenomenon
chosen
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.
-
B.
geological event
A geological event is a natural occurrence resulting from Earth’s internal or surface processes, such as earthquakes, volcanic eruptions, landslides, or tectonic shifts, that alters the planet’s physical structure or landscape.
-
C.
evolutionary event
An evolutionary event is a discrete occurrence or process, such as mutation, selection, speciation, or extinction, that alters the genetic composition, traits, or lineage relationships of organisms over time.
-
D.
disaster
A disaster is a sudden, disruptive event—natural or human-made—that causes significant harm to people, property, or the environment and overwhelms normal coping capacities.
-
E.
volcanic event
A volcanic event is a geologic occurrence in which magma, gases, and volcanic materials are erupted or otherwise released from a volcano or fissure, potentially altering the surrounding environment.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.