Triple

T22681268
Position Surface form Disambiguated ID Type / Status
Subject Gunpowder Magazine E560486 entity
Predicate riskMitigationPurpose P117906 FINISHED
Object prevent accidental explosions 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: prevent accidental explosions | Statement: [Gunpowder Magazine, riskMitigationPurpose, prevent accidental explosions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: riskMitigationPurpose
Context triple: [Gunpowder Magazine, riskMitigationPurpose, prevent accidental explosions]
  • A. riskManagementGoal
    Indicates the objective or desired outcome that guides how risks are identified, assessed, and controlled within a risk management process.
  • B. riskPractice
    Indicates that an entity engages in or is associated with a practice, behavior, or procedure that carries a potential for harm, loss, or adverse outcomes.
  • C. riskReductionFor chosen
    Indicates a relationship where one entity decreases or mitigates the level of risk associated with another entity or situation.
  • D. riskManagement
    Indicates the implementation of strategies and actions to identify, assess, and mitigate potential risks associated with an entity or activity.
  • E. riskAddressed
    Indicates that a particular risk has been identified and is being mitigated, managed, or otherwise handled by an associated action, control, or measure.
  • 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_69e2454bfd00819099115715a22cb057 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1786027648190972d1b0bbe81ed13 completed April 29, 2026, 3:17 a.m.
PD Predicate disambiguation batch_69ee62a6245881909506ff502da14137 completed April 26, 2026, 7:08 p.m.
Created at: April 17, 2026, 3:12 p.m.