Triple
T1840726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Indian Ocean earthquake and tsunami |
E41170
|
entity |
| Predicate | tsunamiCause |
P23012
|
FINISHED |
| Object | seafloor displacement due to megathrust fault rupture |
—
|
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: seafloor displacement due to megathrust fault rupture | Statement: [2004 Indian Ocean earthquake and tsunami, tsunamiCause, seafloor displacement due to megathrust fault rupture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiCause Context triple: [2004 Indian Ocean earthquake and tsunami, tsunamiCause, seafloor displacement due to megathrust fault rupture]
-
A.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
-
B.
producedTsunami
chosen
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
-
C.
hasTsunamiRisk
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
-
D.
tsunamiSourceRegion
Indicates the geographic region or area from which a tsunami originates or is generated.
-
E.
earthquakeType
Indicates the specific classification or category of an earthquake based on its characteristics or cause.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.