Triple
T35326920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crater Peak |
E1020211
|
entity |
| Predicate | hadSignificantEruption |
P7369
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [Crater Peak, hadSignificantEruption, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSignificantEruption Context triple: [Crater Peak, hadSignificantEruption, 1953]
-
A.
erupted
Indicates that a volcano or similar geological feature suddenly expelled lava, ash, gas, or other material in a violent outburst.
-
B.
eruptedThrough
Indicates that one entity forcefully broke out from within and passed through another entity, typically in a sudden or violent manner.
-
C.
hasEruptionEpisodes
Indicates that an entity (such as a volcano or geyser) undergoes one or more distinct eruption events over time.
-
D.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
E.
notableEruption
chosen
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
- 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_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.