Triple
T25099247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariveles Mountain Complex |
E628677
|
entity |
| Predicate | eruptiveNature |
P106693
|
FINISHED |
| Object | potentially active volcano |
—
|
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: potentially active volcano | Statement: [Mariveles Mountain Complex, eruptiveNature, potentially active volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptiveNature Context triple: [Mariveles Mountain Complex, eruptiveNature, potentially active volcano]
-
A.
eruptionPhenomena
Indicates the specific observable events or manifestations that occur during a volcanic eruption.
-
B.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
-
C.
eruptionPotential
chosen
Indicates the likelihood or capacity of something (typically a volcano or similar system) to erupt under given conditions.
-
D.
eruptiveEnvironment
Indicates the geological or environmental setting in which an eruption or eruptive activity occurs.
-
E.
volcanismType
Indicates the specific kind or style of volcanic activity or processes associated with an entity.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464bb4a288190909cfe145f9cbaa5 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:25 a.m.