Triple
T811532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | atomic bombings of Hiroshima and Nagasaki |
E17555
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | use of nuclear weapons in warfare |
C895
|
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: use of nuclear weapons in warfare Context triple: [atomic bombings of Hiroshima and Nagasaki, instanceOf, use of nuclear weapons in warfare]
-
A.
nuclear weapon
A nuclear weapon is a highly destructive explosive device that releases immense energy through nuclear fission, fusion, or a combination of both, causing catastrophic blast, heat, and radiation effects.
-
B.
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.
-
C.
nuclear weapons proposal
A nuclear weapons proposal is a formal plan or document outlining the development, acquisition, deployment, or modification of nuclear armaments, including their strategic rationale, technical specifications, and anticipated impacts.
-
D.
nuclear attack
chosen
A nuclear attack is a deliberate military or terrorist action involving the detonation or threatened use of nuclear weapons to cause massive destruction, casualties, and strategic disruption.
-
E.
nuclear weapons crisis
A nuclear weapons crisis is a high-stakes international confrontation in which the use or threatened use of nuclear arms becomes a realistic possibility, creating urgent risks of catastrophic escalation and intense diplomatic, military, and political pressure to resolve the conflict.
- F. None of above.
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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.