Triple
T2649679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubinas volcano |
E53866
|
entity |
| Predicate | hazardStatus |
P16293
|
FINISHED |
| Object | one of the most hazardous volcanoes in Peru |
—
|
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: one of the most hazardous volcanoes in Peru | Statement: [Ubinas volcano, hazardStatus, one of the most hazardous volcanoes in Peru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardStatus Context triple: [Ubinas volcano, hazardStatus, one of the most hazardous volcanoes in Peru]
-
A.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
B.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
-
C.
hasNotableHazard
chosen
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
D.
hasHazardSignage
Indicates that appropriate warning or hazard signs are present to alert people to potential dangers associated with the entity.
-
E.
hasNavigationHazardRelevance
Indicates that something is relevant to, affected by, or poses a potential hazard to navigation.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91ca1288190ba302b04bac4c153 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.