Triple
T19147160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ou Mountains |
E468708
|
entity |
| Predicate | hasGeohazard |
P44599
|
FINISHED |
| Object | volcanic eruptions |
—
|
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: volcanic eruptions | Statement: [Ou Mountains, hasGeohazard, volcanic eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeohazard Context triple: [Ou Mountains, hasGeohazard, volcanic eruptions]
-
A.
geologicalHazardZoneFor
Indicates a relationship where a specified area or zone is identified as being at risk from a particular geological hazard (such as earthquakes, landslides, or volcanic activity).
-
B.
hasNaturalHazardRisk
chosen
Indicates that an entity is exposed or subject to potential damage or impact from one or more natural hazards (e.g., earthquakes, floods, storms).
-
C.
geologicHazardLevel
Indicates the degree of potential danger or risk posed by geologic processes or conditions at a given location.
-
D.
hasVolcanicHazardMap
Indicates that a location or area is associated with an existing volcanic hazard map that documents potential volcanic risks there.
-
E.
hasAvalancheRisk
Indicates that there is a potential or assessed danger of an avalanche occurring in relation to the referenced entity.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e97a79a48190b243553023bf9081 |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.