Triple
T1840637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumatra subduction zone |
E41168
|
entity |
| Predicate | tsunamiHazardLevel |
P24786
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [Sumatra subduction zone, tsunamiHazardLevel, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tsunamiHazardLevel Context triple: [Sumatra subduction zone, tsunamiHazardLevel, very high]
-
A.
hasTsunamiRisk
chosen
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
-
B.
tsunamiGenerated
Indicates that a tsunami is produced or caused by a particular event or source.
-
C.
producedTsunami
Indicates that an event or phenomenon caused or generated a tsunami as a consequence.
-
D.
tsunamiSourceRegion
Indicates the geographic region or area from which a tsunami originates or is generated.
-
E.
experiencedMajorTsunami
Indicates that the subject has undergone or been affected by a large-scale, significant tsunami event.
- 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.