Triple
T31502179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Gorgonio Pass thrust fault system |
E803716
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | thrust fault system |
C35008
|
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 system Context triple: [San Gorgonio Pass thrust fault system, instanceOf, thrust fault system]
-
A.
thrust fault
A thrust fault is a type of reverse fault where rock layers are pushed up and over adjacent rocks at a low angle, typically due to compressional tectonic forces.
-
B.
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.
-
C.
fault system
chosen
A fault system is a network of related fractures in the Earth's crust along which movement has occurred, collectively accommodating and distributing tectonic strain.
-
D.
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.
-
E.
subduction-zone megathrust fault
A subduction-zone megathrust fault is a large, gently dipping fault at the interface between a descending oceanic plate and an overriding plate, where immense stresses accumulate and are released in powerful earthquakes and tsunamis.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:45 p.m.