Triple
T8520040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triassic–Jurassic extinction event |
E201672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geological boundary event |
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: geological boundary event Context triple: [Triassic–Jurassic extinction event, instanceOf, geological boundary event]
-
A.
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.
-
B.
geological boundary
A geological boundary is a conceptual division in the Earth's crust that separates distinct rock units, layers, or geological features based on differences in age, composition, structure, or formation history.
-
C.
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.
-
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.
plate boundary
A plate boundary is the region where two or more tectonic plates meet and interact, often causing earthquakes, volcanic activity, and mountain building.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:16 p.m.