Triple
T33010705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazi biological weapons program |
E844637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biological weapons program |
C59898
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: biological weapons program Context triple: [Nazi biological weapons program, instanceOf, biological weapons program]
-
A.
biological weapon
A biological weapon is a device or agent that deliberately uses pathogens or toxins to cause disease or death in humans, animals, or plants for hostile purposes.
-
B.
biological weapons research facility
A biological weapons research facility is a secure, specialized laboratory complex where scientists develop, test, and sometimes produce pathogenic agents or toxins intended for use in warfare or hostile activities.
-
C.
chemical weapons research program
A chemical weapons research program is an organized effort, typically by a state or military entity, to design, develop, test, and sometimes produce toxic chemical agents and their delivery systems for use in warfare or coercion.
-
D.
nuclear weapons program
A nuclear weapons program is an organized, often state-led effort to research, develop, test, produce, and maintain nuclear warheads and their delivery systems for military deterrence or potential use.
-
E.
biological threat category
A biological threat category is a classification of biological agents or hazards based on their potential to cause harm to human, animal, or environmental health, considering factors such as transmissibility, severity, and required containment measures.
- F. None of above. chosen
Provenance (1 batch)
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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:23 a.m.