Triple
T1840727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Indian Ocean earthquake and tsunami |
E41170
|
entity |
| Predicate | maximumTsunamiHeight |
P34012
|
FINISHED |
| Object | over 30 meters in some locations |
—
|
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: over 30 meters in some locations | Statement: [2004 Indian Ocean earthquake and tsunami, maximumTsunamiHeight, over 30 meters in some locations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTsunamiHeight Context triple: [2004 Indian Ocean earthquake and tsunami, maximumTsunamiHeight, over 30 meters in some locations]
-
A.
producedTsunami
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
-
B.
hasTsunamiRisk
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
-
C.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
-
D.
stormSurgeHeight_feet
Indicates the height of the storm surge, measured in feet, typically above a defined reference level such as normal tide.
-
E.
maximumHeightAboveSeafloor
Indicates the greatest vertical distance between an object or feature and the seafloor beneath it.
- 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_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. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.