Triple
T32392880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galeras Volcano |
E827721
|
entity |
| Predicate | hasEvacuationPlans |
P174025
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Galeras Volcano, hasEvacuationPlans, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvacuationPlans Context triple: [Galeras Volcano, hasEvacuationPlans, yes]
-
A.
hasEvacuationZone
Indicates that a specified area or location falls within a designated evacuation zone associated with another entity (such as an event, hazard, or authority).
-
B.
hasEvacuationTarget
Indicates that an entity has a designated location or destination to which it should be evacuated in an emergency or contingency situation.
-
C.
evacuationMethod
Indicates the means or procedure by which people or objects are removed from a place of danger or risk.
-
D.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
E.
evacuatedDuring
Indicates that one entity was removed or relocated from a place or situation during the time period or event represented by the other entity.
- F. None of above. chosen
Provenance (4 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2110790819083172d8a7bc831ce |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:52 a.m.