Triple
T18934886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunaska volcanoes |
E463215
|
entity |
| Predicate | eruptionEvidence |
P133864
|
FINISHED |
| Object | Holocene volcanic activity |
—
|
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: Holocene volcanic activity | Statement: [Yunaska volcanoes, eruptionEvidence, Holocene volcanic activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionEvidence Context triple: [Yunaska volcanoes, eruptionEvidence, Holocene volcanic activity]
-
A.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
B.
eruptionPhenomena
Indicates the specific observable events or manifestations that occur during a volcanic eruption.
-
C.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
-
D.
eruptionFocus
Indicates that an eruption event is centered on, originates from, or is primarily associated with a particular focal location or feature.
-
E.
eruptionPotential
Indicates the likelihood or capacity of something (typically a volcano or similar system) to erupt under given conditions.
- F. None of above. chosen
Provenance (4 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e6a8208190973669cae439a91e |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.