Triple
T8356808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Boundary Stratotype Section and Point for base of Hettangian |
E196701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geological boundary stratotype |
C19387
|
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 stratotype Context triple: [Global Boundary Stratotype Section and Point for base of Hettangian, instanceOf, geological boundary stratotype]
-
A.
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.
-
B.
geological reference section
chosen
A geological reference section is a formally designated, well-exposed sequence of rock layers used as a standard for describing, correlating, and comparing the stratigraphy of a particular geological unit or region.
-
C.
stratigraphic unit
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.
-
D.
geological basin
A geological basin is a large, low-lying structural depression in the Earth's crust where sediments accumulate over time, often forming significant stratigraphic and resource-bearing sequences.
-
E.
geographical boundary
A geographical boundary is a defined line or zone on the Earth's surface that separates distinct political, cultural, or natural regions.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:59 p.m.