Triple
T6308460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avachinsky volcano |
E141436
|
entity |
| Predicate | hasHistoricEruptions |
P69768
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Avachinsky volcano, hasHistoricEruptions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricEruptions Context triple: [Avachinsky volcano, hasHistoricEruptions, true]
-
A.
hasLastEruptionCentury
Indicates the century during which the most recent eruption of a volcano (or eruptive feature) occurred.
-
B.
eruptionObserved
chosen
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
C.
previousNotableEruption
Indicates that one volcanic eruption directly precedes another notable eruption in time.
-
D.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
E.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given entity.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0647d38008190abaf96632712ddf9 |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:28 p.m.