Triple
T13308386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lituya Bay |
E316994
|
entity |
| Predicate | megatsunamiTrigger |
P77048
|
FINISHED |
| Object | earthquake |
—
|
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: earthquake | Statement: [Lituya Bay, megatsunamiTrigger, earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: megatsunamiTrigger Context triple: [Lituya Bay, megatsunamiTrigger, earthquake]
-
A.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
-
B.
producedTsunami
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
-
C.
tsunamiType
Indicates the specific classification or category of a tsunami associated with an event or location.
-
D.
tsunamiGenerationMechanism
chosen
Indicates the physical process or cause by which a tsunami is produced (e.g., earthquake, landslide, volcanic activity).
-
E.
notableTsunamiEvent
Indicates that a tsunami event is of particular significance or prominence, such as being historically important, unusually large, or widely recognized.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.