Triple
T24366638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasur Volcano |
E614211
|
entity |
| Predicate | hazardLevelSystem |
P155938
|
FINISHED |
| Object | alert level scale used by Vanuatu authorities |
—
|
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: alert level scale used by Vanuatu authorities | Statement: [Yasur Volcano, hazardLevelSystem, alert level scale used by Vanuatu authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardLevelSystem Context triple: [Yasur Volcano, hazardLevelSystem, alert level scale used by Vanuatu authorities]
-
A.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
B.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
C.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
D.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
-
E.
geologicHazardLevel
Indicates the degree of potential danger or risk posed by geologic processes or conditions at a given location.
- F. None of above. chosen
Provenance (4 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2938809f081908abf33edb62ed7f8 |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:01 a.m.