Triple
T37828261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ShakeAlert earthquake early warning system |
E943124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | earthquake early warning system |
C65665
|
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: earthquake early warning system Context triple: [ShakeAlert earthquake early warning system, instanceOf, earthquake early warning system]
-
A.
earthquake monitoring center
An earthquake monitoring center is a facility that continuously collects, analyzes, and disseminates seismic data to detect earthquakes, assess their impact, and support early warning and emergency response efforts.
-
B.
earthquake catalog
An earthquake catalog is a systematically compiled database that records the occurrence, location, magnitude, and other key parameters of earthquakes over a specified region and time period.
-
C.
induced earthquake
An induced earthquake is a seismic event triggered by human activities that alter the stress conditions in the Earth's crust, 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.
seismic hazard model
A seismic hazard model is a conceptual representation that estimates the likelihood and intensity of earthquake shaking at a site or region over a specified time period, based on geological, seismological, and geotechnical data.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.