Triple

T25830171
Position Surface form Disambiguated ID Type / Status
Subject Nuclear, Biological, and Chemical (NBC) Operations Unit E650639 entity
Predicate typeOfThreatHandled P149086 FINISHED
Object radiological threats 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: radiological threats | Statement: [Nuclear, Biological, and Chemical (NBC) Operations Unit, typeOfThreatHandled, radiological threats]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfThreatHandled
Context triple: [Nuclear, Biological, and Chemical (NBC) Operations Unit, typeOfThreatHandled, radiological threats]
  • A. threatsDefendedAgainst chosen
    Indicates a relationship where one entity protects another from specific dangers, attacks, or harmful actions.
  • B. recognizesThreat
    Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
  • C. hasThreatType
    Indicates that an entity is associated with, or characterized by, a specific type or category of threat.
  • D. hasThreats
    Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
  • E. systemThreatType
    Indicates the category or nature of threat that a system poses or is exposed to.
  • 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_69e7ab37438081908f1ccf6284839520 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f7688dd3d08190ad13d0e780570a1c completed May 3, 2026, 3:23 p.m.
PD Predicate disambiguation batch_69f767fcf2f881908bacc7bfc38e68a5 completed May 3, 2026, 3:21 p.m.
Created at: April 22, 2026, 7:38 a.m.