Triple
T9796285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoNet |
E237725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geological hazard monitoring network |
C25752
|
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: geological hazard monitoring network Context triple: [GeoNet, instanceOf, geological hazard monitoring network]
-
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.
geohazards risk reduction program
A geohazards risk reduction program is a coordinated set of policies, practices, and interventions designed to identify, assess, and mitigate risks from geological hazards such as earthquakes, landslides, and volcanic eruptions to protect people, infrastructure, and the environment.
-
C.
environmental observation network
chosen
An environmental observation network is a coordinated system of sensors, platforms, and data infrastructure designed to continuously monitor, collect, and share information about environmental conditions across spatial and temporal scales.
-
D.
GNSS reference network
A GNSS reference network is a coordinated system of continuously operating GNSS stations that provide precise, stable positioning and timing references for surveying, navigation, and geospatial applications.
-
E.
geological survey
A geological survey is a systematic investigation and mapping of the Earth's materials, structures, and processes to understand subsurface conditions and support resource management, hazard assessment, and land-use planning.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:28 p.m.