Triple
T23377832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makran subduction zone |
E593654
|
entity |
| Predicate | historicalTsunami |
P102147
|
FINISHED |
| Object | 1945 Makran tsunami |
—
|
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: 1945 Makran tsunami | Statement: [Makran subduction zone, historicalTsunami, 1945 Makran tsunami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTsunami Context triple: [Makran subduction zone, historicalTsunami, 1945 Makran tsunami]
-
A.
notableTsunamiEvent
chosen
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.
disasterHistory
Indicates that there is a record of past disasters or catastrophic events associated with the entity.
-
D.
oceanCrossingTsunami
Indicates a tsunami event that travels across an ocean basin from its origin to distant shores.
-
E.
tsunamiDate
Indicates the date on which a tsunami event occurred or is recorded.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b526ec8190b0304c72a9010abb |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:33 p.m.