Triple
T17198364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Tsunami Warning Center |
E417412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tsunami warning center |
C37526
|
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: tsunami warning center Context triple: [Pacific Tsunami Warning Center, instanceOf, tsunami warning center]
-
A.
tsunami warning coordination body
chosen
A tsunami warning coordination body is an organization responsible for detecting tsunami threats, issuing timely alerts, and coordinating communication and response efforts among authorities, emergency services, and the public.
-
B.
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.
-
C.
lahar warning system
A lahar warning system is an integrated network of sensors, communication tools, and decision protocols designed to detect volcanic mudflows in real time and rapidly alert at-risk communities and authorities.
-
D.
seismological research institute
A seismological research institute is an organization dedicated to studying earthquakes and Earth's internal structure through seismic data collection, analysis, and modeling to improve hazard assessment and scientific understanding.
-
E.
Volcanic Ash Advisory Centre
A Volcanic Ash Advisory Centre is a specialized meteorological facility responsible for monitoring volcanic eruptions and providing timely warnings and forecasts about volcanic ash clouds to ensure aviation safety.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:38 a.m.