Triple
T32545788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1964 Alaska earthquake |
E831843
|
entity |
| Predicate | deathsFromTsunami |
P179965
|
FINISHED |
| Object | majority of total deaths |
—
|
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: majority of total deaths | Statement: [1964 Alaska earthquake, deathsFromTsunami, majority of total deaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathsFromTsunami Context triple: [1964 Alaska earthquake, deathsFromTsunami, majority of total deaths]
-
A.
notableTsunamiEvent
Indicates that a tsunami event is of particular significance or prominence, such as being historically important, unusually large, or widely recognized.
-
B.
producedTsunami
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
-
C.
tsunamiAffectedCountry
Indicates that a given country has been impacted by a tsunami event, such as through damage, casualties, or disruption.
-
D.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
-
E.
earthquakeCasualties
Indicates that an earthquake event resulted in a specified number or set of casualties (deaths and/or injuries).
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: May 1, 2026, 1:02 a.m.