Triple
T9870683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RT-2PM Topol |
E239947
|
entity |
| Predicate | coldLaunchCapability |
P90977
|
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: [RT-2PM Topol, coldLaunchCapability, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coldLaunchCapability Context triple: [RT-2PM Topol, coldLaunchCapability, true]
-
A.
hasVerticalLaunchSystem
Indicates that one entity is equipped with a vertical launch system used to fire missiles or similar munitions vertically.
-
B.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
C.
usesLaunchVehicleCore
Indicates that a space mission or launch event makes use of a specific launch vehicle core as part of its propulsion or structural stack.
-
D.
usesLaunchVehicleBooster
Indicates that a launch vehicle employs a specific booster as part of its propulsion system during launch.
-
E.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3d62628819094786a49b9bcd09b |
completed | April 2, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:36 p.m.