Triple
T28817567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhaetian Stage |
E727681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Upper Triassic stage |
C55259
|
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: Upper Triassic stage Context triple: [Rhaetian Stage, instanceOf, Upper Triassic stage]
-
A.
Devonian boundary
The Devonian boundary is a stratigraphic demarcation that marks the beginning or end of the Devonian Period in Earth's geologic timescale, defined by globally recognized changes in rock layers and fossil assemblages.
-
B.
Upper Cretaceous stage
The Upper Cretaceous stage is a late subdivision of the Cretaceous Period characterized by widespread marine transgressions, diverse dinosaur and marine reptile faunas, and the lead-up to the mass extinction at the Cretaceous–Paleogene boundary.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:33 a.m.