Triple
T2659735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagan |
E54697
|
entity |
| Predicate | evacuationEvent |
P23041
|
FINISHED |
| Object | 1981 evacuation due to eruption |
—
|
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: 1981 evacuation due to eruption | Statement: [Pagan, evacuationEvent, 1981 evacuation due to eruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuationEvent Context triple: [Pagan, evacuationEvent, 1981 evacuation due to eruption]
-
A.
notableEvacuation
chosen
Indicates a significant, widely recognized instance of people being moved or fleeing from a place for safety, typically due to danger or emergency conditions.
-
B.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
-
C.
emergencyEvent
Indicates that an urgent, unexpected, and potentially harmful situation or incident has occurred requiring immediate attention or response.
-
D.
emergencyResponse
Indicates a relationship where an entity takes immediate action to address or manage an urgent or critical situation.
-
E.
allegedRescueEvent
Indicates that an event is claimed or reported to be a rescue, but its occurrence or nature is not confirmed as factual.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94f3b1881909bd36cfe61c254a5 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.