Triple
T15016206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States nuclear triad |
E377964
|
entity |
| Predicate | threatTypeDeterrence |
P116391
|
FINISHED |
| Object | nuclear 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: nuclear weapons | Statement: [United States nuclear triad, threatTypeDeterrence, nuclear weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatTypeDeterrence Context triple: [United States nuclear triad, threatTypeDeterrence, nuclear weapons]
-
A.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
B.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
C.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
D.
deterrentPosture
Indicates a stance or set of actions intended to discourage or prevent another party from taking hostile or undesired actions.
-
E.
perceivedThreat
Indicates that one entity regards another entity or situation as potentially harmful, dangerous, or adverse.
- F. None of above. chosen
Provenance (4 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7633fcc8190b2231f43252bc46f |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:55 a.m.