Triple
T17743004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W78 warhead |
E442909
|
entity |
| Predicate | nuclearExplosiveType |
P128827
|
FINISHED |
| Object | boosted primary with thermonuclear secondary |
—
|
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: boosted primary with thermonuclear secondary | Statement: [W78 warhead, nuclearExplosiveType, boosted primary with thermonuclear secondary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearExplosiveType Context triple: [W78 warhead, nuclearExplosiveType, boosted primary with thermonuclear secondary]
-
A.
explosionType
Indicates the specific kind or category of explosion associated with an event or entity.
-
B.
bombType
Indicates the specific kind or category of bomb associated with an event, object, or action.
-
C.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
D.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
E.
explosionMechanism
Indicates the specific process or mechanism by which an explosion is initiated or occurs.
- 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.