Triple
T23377818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makran subduction zone |
E593654
|
entity |
| Predicate | tsunamiHazard |
P24786
|
FINISHED |
| Object | capable of generating large tsunamis |
—
|
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: capable of generating large tsunamis | Statement: [Makran subduction zone, tsunamiHazard, capable of generating large tsunamis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiHazard Context triple: [Makran subduction zone, tsunamiHazard, capable of generating large tsunamis]
-
A.
hasTsunamiRisk
chosen
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
-
B.
tsunamiWarning
Indicates that an official alert has been issued warning that a tsunami is expected or possible in a specified area.
-
C.
tsunamiType
Indicates the specific classification or category of a tsunami associated with an event or location.
-
D.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
-
E.
producedTsunami
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
- 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.