Triple
T35326924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crater Peak |
E1020211
|
entity |
| Predicate | producedPyroclasticFlows |
P123824
|
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, producedPyroclasticFlows, 1992 eruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedPyroclasticFlows Context triple: [Crater Peak, producedPyroclasticFlows, 1992 eruption]
-
A.
producedEruption
Indicates that an entity caused or generated a particular eruption event.
-
B.
hasPyroclasticDeposits
Indicates that an entity exhibits or contains accumulations of pyroclastic volcanic material deposited by explosive eruptions.
-
C.
hasVolcanicProduct
chosen
Indicates that an entity possesses, contains, or is associated with material or products originating from volcanic activity.
-
D.
eruptionEvidence
Indicates that there is observable or documented evidence supporting the occurrence of a volcanic eruption.
-
E.
materialErupted
Indicates that some material has been expelled or discharged forcefully from a source, such as through an eruption or sudden outburst.
- 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_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 3, 2026, 4:03 p.m.