Triple
T32545785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1964 Alaska earthquake |
E831843
|
entity |
| Predicate | tsunamiMaximumRunupInAlaska |
P34012
|
FINISHED |
| Object | approximately 67 meters |
—
|
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: approximately 67 meters | Statement: [1964 Alaska earthquake, tsunamiMaximumRunupInAlaska, approximately 67 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiMaximumRunupInAlaska Context triple: [1964 Alaska earthquake, tsunamiMaximumRunupInAlaska, approximately 67 meters]
-
A.
maximumTsunamiHeight
chosen
Indicates the greatest recorded or expected vertical height reached by a tsunami at a given location or event.
-
B.
maximumTsunamiHeightLocation
Indicates the location at which the tsunami reaches its maximum recorded or predicted height.
-
C.
tsunamiArrivalTime
Indicates the specific time at which a tsunami reaches a given location.
-
D.
producedTsunami
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
-
E.
hasTsunamiRisk
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5bfe55881909a20ef79180d19c4 |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.