Triple
T24995728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-880 |
E625562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | S-200 missile variant |
C17786
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: S-200 missile variant Context triple: [V-880, instanceOf, S-200 missile variant]
-
A.
anti-ship missile variant
An anti-ship missile variant is a specific version of a naval strike missile adapted or modified from a base design to optimize performance, guidance, payload, or launch platform compatibility against maritime targets.
-
B.
MiG-29 derivative
A MiG-29 derivative is any aircraft design or variant that evolves from the original MiG-29 Fulcrum platform, incorporating modifications in structure, avionics, propulsion, or mission role while retaining its core aerodynamic and design lineage.
-
C.
Su-30 variant
A Su-30 variant is a specific model within the Su-30 family of twin-engine, multirole fighter aircraft, distinguished by customized avionics, weapons systems, and structural modifications tailored to the requirements of a particular operator or mission profile.
-
D.
anti-armor missile
An anti-armor missile is a guided munition designed specifically to detect, track, and destroy armored targets such as tanks and armored vehicles using high-penetration warheads.
-
E.
self-propelled surface-to-air missile system
chosen
A self-propelled surface-to-air missile system is a mobile, ground-based weapons platform that integrates its own propulsion, radar, and missile launch capabilities to detect, track, and engage airborne targets.
- F. None of above.
Provenance (1 batch)
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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:04 a.m.