Triple
T21905567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Givetian–Frasnian boundary |
E540927
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Devonian boundary |
C45493
|
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: Devonian boundary Context triple: [Givetian–Frasnian boundary, instanceOf, Devonian boundary]
-
A.
Cambrian series
Cambrian series are formal chronostratigraphic subdivisions of the Cambrian System, each representing a distinct interval of early Paleozoic geological time characterized by specific fossil assemblages and rock strata.
-
B.
subdivision of the Ordovician Period
A subdivision of the Ordovician Period is a formally defined interval of geologic time within the Ordovician, used to organize and correlate rock layers and fossil records on a finer temporal scale.
-
C.
subdivision of the Permian Period
A subdivision of the Permian Period is a formally defined interval of geologic time within the Permian, used to organize and correlate rock layers and fossil records on a finer temporal scale.
-
D.
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.
-
E.
Paleozoic fossil group
A Paleozoic fossil group is a collection of fossilized organisms from the Paleozoic Era (about 541–252 million years ago) that share common characteristics and are used to study ancient marine and terrestrial ecosystems, evolutionary patterns, and geological time.
- F. None of above. chosen
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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:35 p.m.