Triple
T24841030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Rift Zone of Tenerife |
E621612
|
entity |
| Predicate | containsEruptionSite |
P7372
|
FINISHED |
| Object | Chinyero volcano |
—
|
NE NERFINISHED |
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: Chinyero volcano | Statement: [Northwest Rift Zone of Tenerife, containsEruptionSite, Chinyero volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEruptionSite Context triple: [Northwest Rift Zone of Tenerife, containsEruptionSite, Chinyero volcano]
-
A.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
B.
eruptionCoincidedWith
Indicates that a volcanic eruption occurred at the same time or within the same temporal interval as another specified event or condition.
-
C.
eruptionEvidence
Indicates that there is observable or documented evidence supporting the occurrence of a volcanic eruption.
-
D.
containsVolcanicRegion
chosen
Indicates that one entity geographically includes or encompasses an area characterized by volcanic features or activity.
-
E.
hasEruptionEpisodes
Indicates that an entity (such as a volcano or geyser) undergoes one or more distinct eruption events over time.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 5:18 a.m.