Triple
T32073436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force de frappe |
E819077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French nuclear deterrent |
C40031
|
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: French nuclear deterrent Context triple: [Force de frappe, instanceOf, French nuclear deterrent]
-
A.
strategic nuclear deterrent
chosen
A strategic nuclear deterrent is a nation's capability, typically comprising long-range nuclear weapons and delivery systems, designed to dissuade adversaries from attacking by threatening devastating retaliatory strikes.
-
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 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.
-
D.
French military presence abroad
The French military presence abroad encompasses all French armed forces deployed outside national territory for defense commitments, international security operations, peacekeeping, crisis response, and support to allies and partner nations.
-
E.
nuclear weapons policy
Nuclear weapons policy is the set of principles, laws, strategies, and international agreements that govern the development, deployment, potential use, and control of nuclear weapons by states and organizations.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:23 a.m.