Triple
T4713206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llaima Volcano |
E104565
|
entity |
| Predicate | hasGlobalVolcanismProgramID |
P57578
|
FINISHED |
| Object | 357120 |
—
|
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: 357120 | Statement: [Llaima Volcano, hasGlobalVolcanismProgramID, 357120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalVolcanismProgramID Context triple: [Llaima Volcano, hasGlobalVolcanismProgramID, 357120]
-
A.
hasGlobalVolcanoProgramID
chosen
Indicates that an entity is associated with a specific identifier assigned by the Global Volcano Program.
-
B.
hasVolcanicAlertLevelSystem
Indicates that an entity employs or is associated with a system for classifying and communicating levels of volcanic alert or hazard.
-
C.
isPartOfVolcanicSystem
Indicates that one entity belongs to, or is a component within, a larger volcanic system or complex.
-
D.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.