Triple
T32731366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transverse Ranges fault system |
E836963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | seismogenic zone |
C58536
|
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: seismogenic zone Context triple: [Transverse Ranges fault system, instanceOf, seismogenic zone]
-
A.
seismotectonic segment
A seismotectonic segment is a distinct portion of a fault or plate boundary characterized by relatively uniform geological and tectonic properties that control its earthquake behavior and rupture patterns.
-
B.
intraplate seismic zone
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.
subduction zone
A subduction zone is a tectonic boundary where one lithospheric plate sinks beneath another into the mantle, generating intense seismic activity, volcanism, and mountain building.
-
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. 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.