Triple
T32158256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand volcano monitoring network |
E821355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geophysical monitoring system |
C26837
|
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: geophysical monitoring system Context triple: [New Zealand volcano monitoring network, instanceOf, geophysical monitoring system]
-
A.
seismological network
chosen
A seismological network is a coordinated system of spatially distributed seismic stations and instruments designed to detect, record, and analyze ground motions from earthquakes and other seismic events.
-
B.
geophysical service
A geophysical service is a specialized operation that applies geophysical methods and technologies to investigate and characterize subsurface conditions for purposes such as resource exploration, environmental assessment, and engineering support.
-
C.
geophysical model
A geophysical model is a mathematical or computational representation of Earth's physical properties and processes used to simulate, interpret, and predict geologic and geodynamic phenomena.
-
D.
ground-based monitoring facility
A ground-based monitoring facility is a terrestrial installation equipped with sensors, instruments, and communication systems used to continuously observe, measure, and report on environmental, geological, atmospheric, or infrastructural conditions.
-
E.
seismological project
A seismological project is an organized scientific effort that designs and conducts studies to measure, analyze, and interpret seismic activity and Earth’s subsurface structures.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:32 a.m.