Triple
T32392882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galeras Volcano |
E827721
|
entity |
| Predicate | hasVolcanicAlertSystem |
P42096
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [Galeras Volcano, hasVolcanicAlertSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicAlertSystem Context triple: [Galeras Volcano, hasVolcanicAlertSystem, yes]
-
A.
hasVolcanicAlertLevelSystem
chosen
Indicates that an entity employs or is associated with a system for classifying and communicating levels of volcanic alert or hazard.
-
B.
hasVolcanicMonitoring
Indicates that an entity is subject to, or equipped with, systems or activities for monitoring volcanic activity.
-
C.
hasLaharWarningSystem
Indicates that an entity is equipped with a system designed to detect and warn about potential or ongoing lahars (volcanic mudflows).
-
D.
volcanicAlertLevelManagedBy
Indicates that the responsibility for monitoring, setting, or updating a volcano’s alert level is held by a specified managing authority or organization.
-
E.
hasVolcanoObservatory
Indicates that a place or region possesses an established volcano observatory facility that monitors volcanic activity there.
- F. None of above.
Provenance (3 batches)
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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 12:52 a.m.