Triple
T9726227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RT-23 Molodets |
E235618
|
entity |
| Predicate | warhead |
P61965
|
FINISHED |
| Object | multiple independently targetable reentry vehicles |
—
|
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: multiple independently targetable reentry vehicles | Statement: [RT-23 Molodets, warhead, multiple independently targetable reentry vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warhead Context triple: [RT-23 Molodets, warhead, multiple independently targetable reentry vehicles]
-
A.
warheadName
Indicates the specific name or designation assigned to a warhead associated with an entity or system.
-
B.
warheadTypes
chosen
Indicates the types or categories of warheads associated with a given weapon or delivery system.
-
C.
warheadMass
Indicates the mass or weight of a warhead associated with an entity or system.
-
D.
warheadEffect
Indicates the type or nature of impact, damage, or outcome produced when a warhead is used or detonated.
-
E.
warheadFuzing
Indicates the method or mechanism by which a warhead is triggered or detonated in relation to its target or flight conditions.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e798c348190885b79d7dffc9d8d |
completed | April 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:21 p.m.