Triple
T17777343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viejo volcano |
E443805
|
entity |
| Predicate | hasEruptiveHistory |
P37550
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Viejo volcano, hasEruptiveHistory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEruptiveHistory Context triple: [Viejo volcano, hasEruptiveHistory, yes]
-
A.
hasEruptiveStyle
Indicates that an entity (typically a volcano or eruption) exhibits a particular manner or pattern of eruptive behavior.
-
B.
hasFrequentEruptionsSince
Indicates that an entity has experienced eruptions repeatedly and at relatively short intervals starting from a specified point in time.
-
C.
hasHistoricalEruptionsSince
Indicates that the referenced volcano or geological feature has experienced one or more recorded eruptions since a specified point in time.
-
D.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
E.
hasEruptionVolume
Indicates the relationship between a volcanic eruption event and the measured volume of material it releases.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871e06a481909cf6d59e49dc21c5 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.