Triple
T22304971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter missile |
E551350
|
entity |
| Predicate | nuclearDeliveryMethod |
P92575
|
FINISHED |
| Object | ballistic trajectory |
—
|
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: ballistic trajectory | Statement: [Jupiter missile, nuclearDeliveryMethod, ballistic trajectory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearDeliveryMethod Context triple: [Jupiter missile, nuclearDeliveryMethod, ballistic trajectory]
-
A.
warheadDeliveryMethod
chosen
Indicates the method or mechanism by which a warhead is transported, deployed, or delivered to its target.
-
B.
airDeliveredNuclearWeapons
Indicates that nuclear weapons were delivered to their target by air, typically via aircraft or air-launched systems.
-
C.
nuclearWeaponsDeliveryNation
Indicates that a nation is responsible for delivering or deploying nuclear weapons, typically as the launching or operating country in a nuclear weapons system.
-
D.
nuclearExplosiveType
Indicates the specific category or kind of nuclear explosive device associated with an entity or event.
-
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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15726b7e48190b7636db01dbb8a40 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.