Triple
T1349651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BioWatch program |
E28851
|
entity |
| Predicate | typeOfThreatMonitored |
P19863
|
FINISHED |
| Object | biological weapons |
—
|
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: biological weapons | Statement: [BioWatch program, typeOfThreatMonitored, biological weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfThreatMonitored Context triple: [BioWatch program, typeOfThreatMonitored, biological weapons]
-
A.
threatTypeAddressed
chosen
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
B.
historicalThreat
Indicates that one entity posed a significant threat to another in the past, but is not necessarily a current or ongoing danger.
-
C.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
D.
oversightTools
Indicates that certain tools or mechanisms are used to monitor, review, or supervise the actions or performance of an entity.
-
E.
Tier1Reporting
Indicates that an entity is subject to primary, highest-priority reporting requirements or obligations within a reporting framework.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c268745481908be649526c18e558 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.