Triple
T386128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lassen Volcanic National Park |
E8782
|
entity |
| Predicate | hasEruptionHistory |
P7369
|
FINISHED |
| Object | 1914–1921 Lassen Peak 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: 1914–1921 Lassen Peak eruptions | Statement: [Lassen Volcanic National Park, hasEruptionHistory, 1914–1921 Lassen Peak eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEruptionHistory Context triple: [Lassen Volcanic National Park, hasEruptionHistory, 1914–1921 Lassen Peak eruptions]
-
A.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
B.
notableEruption
chosen
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
C.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given entity.
-
D.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
E.
volcanicStatus
Indicates the current activity state or condition of a volcano, such as active, dormant, or extinct.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec447b5481908a5a084787b44ced |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.