Triple
T13077143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Popo |
E329606
|
entity |
| Predicate | hasEruptions |
P2857
|
FINISHED |
| Object | frequent explosive 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: frequent explosive eruptions | Statement: [El Popo, hasEruptions, frequent explosive eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEruptions Context triple: [El Popo, hasEruptions, frequent explosive eruptions]
-
A.
hasFrequentEruptionsSince
Indicates that an entity has experienced eruptions repeatedly and at relatively short intervals starting from a specified point in time.
-
B.
hasVolcanicActivity
chosen
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
C.
hasHistoricalEruptionsSince
Indicates that the referenced volcano or geological feature has experienced one or more recorded eruptions since a specified point in time.
-
D.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
E.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9811828448190ac6ddd3e9c221251 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:01 p.m.