Triple
T17114544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phanerozoic mass extinctions |
E415306
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mass extinction event series |
C12880
|
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: mass extinction event series Context triple: [Phanerozoic mass extinctions, instanceOf, mass extinction event series]
-
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.
evolutionary event
chosen
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.
-
C.
carbon isotope excursion
A carbon isotope excursion is a geologically rapid, significant shift in the ratio of stable carbon isotopes (typically δ13C) recorded in sediments or fossils, reflecting major changes in the global carbon cycle and often associated with climatic or biotic events.
-
D.
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.
-
E.
prehistoric event
A prehistoric event is a significant occurrence or series of occurrences that took place before the advent of written records, known primarily through archaeological, geological, and paleontological evidence.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.