Triple
T14693994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continuous At-Sea Deterrent |
E345105
|
entity |
| Predicate | nuclearWeaponType |
P61965
|
FINISHED |
| Object | strategic 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: strategic nuclear weapons | Statement: [Continuous At-Sea Deterrent, nuclearWeaponType, strategic nuclear weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearWeaponType Context triple: [Continuous At-Sea Deterrent, nuclearWeaponType, strategic nuclear weapons]
-
A.
warheadTypes
chosen
Indicates the types or categories of warheads associated with a given weapon or delivery system.
-
B.
isStrategicWeapon
Indicates that the weapon is designed or classified for large-scale, long-range, or high-impact strategic use rather than for tactical or localized operations.
-
C.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
D.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
-
E.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb586e7108190be644db9cf9a4d99 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.