Triple
T13656866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocene catastrophic flooding of the Black Sea |
E326884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | paleogeographic event hypothesis |
C4521
|
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: paleogeographic event hypothesis Context triple: [Holocene catastrophic flooding of the Black Sea, instanceOf, paleogeographic event hypothesis]
-
A.
paleozoogeographic event
A paleozoogeographic event is a past occurrence or process that altered the geographic distribution, dispersal pathways, or community composition of animal life through geological time.
-
B.
biogeographic event
A biogeographic event is a historical or contemporary occurrence (such as dispersal, vicariance, extinction, or range expansion) that alters the geographic distribution of organisms or lineages.
-
C.
supercontinent cycle
The supercontinent cycle is the long-term geologic process in which Earth's continental plates repeatedly assemble into a single massive landmass (a supercontinent) and then break apart over hundreds of millions of years.
-
D.
geological event
chosen
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.
-
E.
geologic time scale
The geologic time scale is a chronological framework that organizes Earth's 4.6-billion-year history into eons, eras, periods, epochs, and ages based on major geological and biological events.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:52 p.m.