Triple
T33584509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W62 warhead |
E860242
|
entity |
| Predicate | nuclearWeaponFamily |
P162933
|
FINISHED |
| Object | U.S. W-series warheads |
—
|
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: U.S. W-series warheads | Statement: [W62 warhead, nuclearWeaponFamily, U.S. W-series warheads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearWeaponFamily Context triple: [W62 warhead, nuclearWeaponFamily, U.S. W-series warheads]
-
A.
nuclearWeapon
Indicates that an entity possesses, involves, or is characterized by nuclear weapons or nuclear-weapon-related capabilities.
-
B.
nuclearWeaponConfiguration
Indicates the specific arrangement, setup, or design characteristics associated with a nuclear weapon or nuclear weapons system.
-
C.
missileFamily
Indicates that one missile belongs to, or is categorized within, the same family or series as another missile.
-
D.
weaponFamily
chosen
Indicates that two weapons belong to the same broader classification or type group based on shared characteristics or lineage.
-
E.
nuclearWeaponsCustodian
Indicates that one entity is responsible for the control, safekeeping, or management of another entity’s nuclear weapons.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:40 a.m.