Triple
T11138148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Chiginagak |
E263466
|
entity |
| Predicate | hasVolcanicHazardMonitoring |
P64414
|
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: [Mount Chiginagak, hasVolcanicHazardMonitoring, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanicHazardMonitoring Context triple: [Mount Chiginagak, hasVolcanicHazardMonitoring, yes]
-
A.
hasVolcanicMonitoring
chosen
Indicates that an entity is subject to, or equipped with, systems or activities for monitoring volcanic activity.
-
B.
hasVolcanicAlertLevelSystem
Indicates that an entity employs or is associated with a system for classifying and communicating levels of volcanic alert or hazard.
-
C.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
D.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
E.
volcanicHazards
Indicates the presence or characterization of dangers and harmful phenomena associated with volcanic activity.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e85f2ea48190bf1ff63af1d7d236 |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.