Triple
T13143360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pucón |
E312268
|
entity |
| Predicate | volcanoStatusNearby |
P8376
|
FINISHED |
| Object | 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: active volcano | Statement: [Pucón, volcanoStatusNearby, active volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volcanoStatusNearby Context triple: [Pucón, volcanoStatusNearby, active volcano]
-
A.
volcanicStatus
chosen
Indicates the current activity state or condition of a volcano, such as active, dormant, or extinct.
-
B.
nearVolcano
Indicates that one entity is located in close proximity to a volcano.
-
C.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
D.
isVolcanicNeighborOf
Indicates that one geographic feature is located close enough to another volcanic feature that they are considered neighboring volcano-related entities.
-
E.
eruptionPotential
Indicates the likelihood or capacity of something (typically a volcano or similar system) to erupt under given conditions.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981d24da48190b99e713878e8d003 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:10 p.m.