Triple

T7358623
Position Surface form Disambiguated ID Type / Status
Subject 2018 Anak Krakatau eruption and tsunami E169688 entity
Predicate warningSystemIssue P56135 FINISHED
Object no earthquake-triggered tsunami warning 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: no earthquake-triggered tsunami warning | Statement: [2018 Anak Krakatau eruption and tsunami, warningSystemIssue, no earthquake-triggered tsunami warning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: warningSystemIssue
Context triple: [2018 Anak Krakatau eruption and tsunami, warningSystemIssue, no earthquake-triggered tsunami warning]
  • A. warningIssued chosen
    Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
  • B. warningType
    Indicates the specific category or classification of a warning associated with an entity or event.
  • C. platformIssue
    Indicates that there is a problem, malfunction, or limitation affecting the operation or availability of a platform.
  • D. raisesIssue
    Indicates that one entity brings up, reports, or formally submits a concern, problem, or topic for attention to another entity or system.
  • E. issueType
    Indicates the specific category or classification assigned to an issue within a tracking or management context.
  • 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_69c68a59f2288190877ca15c19b1e822 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f26d6d6081909c7272a9ccae0d97 completed March 27, 2026, 9:11 p.m.
PD Predicate disambiguation batch_69c6f02d36108190bcb34a95e6a30bd7 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:06 p.m.