Triple
T28817352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibex Zone |
E727674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biostratigraphic subdivision |
C1098
|
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: biostratigraphic subdivision Context triple: [Ibex Zone, instanceOf, biostratigraphic subdivision]
-
A.
stratigraphic unit
chosen
A stratigraphic unit is a volume of rock or sediment defined and distinguished from adjacent material by its recognizable and mappable physical, chemical, or paleontological characteristics and its position in the geological record.
-
B.
chronostratigraphic chart
A chronostratigraphic chart is a diagram that organizes rock layers and geological events in chronological order to illustrate the relative timing and duration of Earth’s stratigraphic units.
-
C.
chronostratigraphic reference point
A chronostratigraphic reference point is a precisely defined boundary in geological time, often marked by a Global Boundary Stratotype Section and Point (GSSP), used to correlate and standardize rock layers and time intervals worldwide.
-
D.
subdivision of the Cretaceous
A subdivision of the Cretaceous is a formally defined interval of geologic time within the Cretaceous Period, used to organize and correlate rock strata and fossil records on a finer temporal scale.
-
E.
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.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:33 a.m.