Triple
T17742977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W78 warhead |
E442909
|
entity |
| Predicate | nuclearWeaponDesign |
P128826
|
FINISHED |
| Object | two-stage thermonuclear |
—
|
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: two-stage thermonuclear | Statement: [W78 warhead, nuclearWeaponDesign, two-stage thermonuclear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearWeaponDesign Context triple: [W78 warhead, nuclearWeaponDesign, two-stage thermonuclear]
-
A.
nuclearWeaponsProgram
Indicates the existence, development, or pursuit of a program related to the research, production, or maintenance of nuclear weapons.
-
B.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
-
C.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
D.
nuclearWeaponsCustodian
Indicates that one entity is responsible for the control, safekeeping, or management of another entity’s nuclear weapons.
-
E.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ace58988190b927ca29af7a8b77 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:09 a.m.