Triple
T35326925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crater Peak |
E1020211
|
entity |
| Predicate | producedLahars |
P95449
|
FINISHED |
| Object | 1992 eruption |
—
|
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: 1992 eruption | Statement: [Crater Peak, producedLahars, 1992 eruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedLahars Context triple: [Crater Peak, producedLahars, 1992 eruption]
-
A.
hasLahars
chosen
Indicates that an entity experiences, produces, or is associated with volcanic mudflows (lahars).
-
B.
hasPotentialForLahars
Indicates that one entity (typically a geographic or volcanic feature) is capable of producing or being affected by lahars under certain conditions.
-
C.
producedEruption
Indicates that an entity caused or generated a particular eruption event.
-
D.
oneOfDeadliestLaharDisasters
Indicates that the event is among the most deadly lahar (volcanic mudflow) disasters in terms of human casualties or impact.
-
E.
hasLaharWarningSystem
Indicates that an entity is equipped with a system designed to detect and warn about potential or ongoing lahars (volcanic mudflows).
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:03 p.m.