Triple
T5005074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keystone Thrust Fault |
E112471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | thrust fault |
C16783
|
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: thrust fault Context triple: [Keystone Thrust Fault, instanceOf, thrust fault]
-
A.
transform fault system
A transform fault system is a network of strike-slip plate boundaries where tectonic plates slide horizontally past each other along fractures in the Earth's crust, often linking segments of mid-ocean ridges or other plate boundaries.
-
B.
strike-slip fault
A strike-slip fault is a fracture in the Earth's crust where blocks of rock slide horizontally past each other, primarily due to shear stress.
-
C.
transform fault
A transform fault is a type of plate boundary where two tectonic plates slide horizontally past each other along a fracture in the Earth's crust, often offsetting segments of mid-ocean ridges and generating earthquakes.
-
D.
crustal block
A crustal block is a relatively rigid, coherent segment of the Earth's crust bounded by faults or other discontinuities that can move or deform as a unit within the larger tectonic framework.
-
E.
intraplate earthquake
An intraplate earthquake is a seismic event that occurs within the interior of a tectonic plate, far from plate boundaries, typically caused by the reactivation of ancient faults or stresses transmitted through the plate.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:35 p.m.