Triple
T33584519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W62 warhead |
E860242
|
entity |
| Predicate | nuclearExplosivePackageType |
P128827
|
FINISHED |
| Object | two-stage Teller–Ulam design |
—
|
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 Teller–Ulam design | Statement: [W62 warhead, nuclearExplosivePackageType, two-stage Teller–Ulam design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearExplosivePackageType Context triple: [W62 warhead, nuclearExplosivePackageType, two-stage Teller–Ulam design]
-
A.
nuclearExplosiveType
chosen
Indicates the specific category or kind of nuclear explosive device associated with an entity or event.
-
B.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
C.
bombType
Indicates the specific kind or category of bomb associated with an event, object, or action.
-
D.
nuclearWeapon
Indicates that an entity possesses, involves, or is characterized by nuclear weapons or nuclear-weapon-related capabilities.
-
E.
explosiveComponents
Indicates that one entity consists of, contains, or is associated with components that are explosive or used to create an explosive device.
- 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_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:40 a.m.