Triple
T8514418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSMC Anchorage (volcanic ash advisory centre) |
E201536
|
entity |
| Predicate | monitorsHazard |
P82386
|
FINISHED |
| Object | volcanic ash clouds |
—
|
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 ash clouds | Statement: [RSMC Anchorage (volcanic ash advisory centre), monitorsHazard, volcanic ash clouds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitorsHazard Context triple: [RSMC Anchorage (volcanic ash advisory centre), monitorsHazard, volcanic ash clouds]
-
A.
monitorsHazardType
chosen
Indicates that an entity observes, tracks, or keeps watch over a specified type or category of hazard.
-
B.
hasObjectiveHazards
Indicates that an entity is associated with concrete, externally verifiable dangers or risks.
-
C.
monitors
Indicates that one entity observes, tracks, or checks the state, behavior, or performance of another entity over time.
-
D.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
E.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe60e12848190a4a3dfa457aef275 |
completed | March 31, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:15 p.m.