Triple
T33584523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W62 warhead |
E860242
|
entity |
| Predicate | designedForMIRV |
P197777
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [W62 warhead, designedForMIRV, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForMIRV Context triple: [W62 warhead, designedForMIRV, true]
-
A.
MIRVStatus
Indicates the status or condition of a multiple independently targetable reentry vehicle (MIRV) capability associated with a given entity or system.
-
B.
missileFamily
Indicates that one missile belongs to, or is categorized within, the same family or series as another missile.
-
C.
notableMissile
Indicates that the subject is a missile distinguished by particular significance, prominence, or noteworthiness (e.g., historical impact, technological importance, or public attention).
-
D.
maximumWarheadsPerMissile
Indicates the greatest number of warheads that a single missile is allowed or able to carry.
-
E.
numberOfMissilesPerLauncher
Indicates the quantity of missiles assigned to or carried by each individual launcher.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69feaa477f7c81909382b3aa77e7e11c |
completed | May 9, 2026, 3:30 a.m. |
Created at: May 1, 2026, 1:40 a.m.