Triple
T6865641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-200 Angara/Vega/Dubna |
E158392
|
entity |
| Predicate | missileDesignation |
P28510
|
FINISHED |
| Object | V-860P |
E625561
|
NE 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: V-860P | Statement: [S-200 Angara/Vega/Dubna, missileDesignation, V-860P]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: V-860P Context triple: [S-200 Angara/Vega/Dubna, missileDesignation, V-860P]
-
A.
V-860
chosen
V-860 is a Soviet-era surface-to-air missile variant associated with the S-200 long-range air defense system.
-
B.
V-880
V-880 is a Soviet-era surface-to-air missile variant associated with the S-200 long-range air defense system.
-
C.
V-600
V-600 is a Soviet-era surface-to-air missile used in the S-125 Neva/Pechora air defense system for engaging low- to medium-altitude aerial targets.
-
D.
P80
P80 is a solid-fuel first-stage rocket motor used on the European Vega small-lift launch vehicle.
-
E.
V8 V-Fusion
V8 V-Fusion is a line of juice beverages that blend vegetable and fruit juices to provide a flavorful drink with added nutritional benefits.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e1cfd8fc81908efb83c061cb8e4f |
completed | March 27, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c748bcb4048190b3860ffdd962d48c |
completed | March 28, 2026, 3:19 a.m. |
Created at: March 27, 2026, 2:21 p.m.