Triple
T14530568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Coast Ranges seismicity |
E340901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional seismicity |
C22773
|
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: regional seismicity Context triple: [California Coast Ranges seismicity, instanceOf, regional seismicity]
-
A.
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.
-
B.
intraplate seismic zone
chosen
An intraplate seismic zone is a region of concentrated earthquake activity that occurs within a tectonic plate, away from its boundaries, due to reactivation of ancient faults or internal plate stresses.
-
C.
induced earthquake zone
An induced earthquake zone is a geographic area where seismic activity is primarily triggered or significantly influenced by human activities such as fluid injection, extraction, or reservoir impoundment.
-
D.
earthquake sequence
An earthquake sequence is a series of temporally and spatially related earthquakes, including mainshocks, foreshocks, and aftershocks, that occur as a fault system adjusts to stress changes in the Earth's crust.
-
E.
interplate earthquake
An interplate earthquake is a seismic event that occurs along the boundary between two tectonic plates as they grind, collide, or slide past one another.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:22 a.m.