Triple
T4569309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siccar Point unconformity |
E122990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geological unconformity |
C3981
|
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 unconformity Context triple: [Siccar Point unconformity, instanceOf, geological unconformity]
-
A.
geological boundary
chosen
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.
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.
-
C.
geologic time interval
A geologic time interval is a span of Earth’s history defined by characteristic rock layers, fossil assemblages, and major geological or biological events, used to organize and correlate geological and paleontological data.
-
D.
geologic time scale
The geologic time scale is a chronological framework that organizes Earth's 4.6-billion-year history into eons, eras, periods, epochs, and ages based on major geological and biological events.
-
E.
geological event
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.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:10 p.m.