Triple
T2911772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVS |
E63696
|
entity |
| Predicate | operatedAircraftModel |
P1524
|
FINISHED |
| Object | Tu-22M |
E61904
|
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: Tu-22M | Statement: [VVS, operatedAircraftModel, Tu-22M]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tu-22M Context triple: [VVS, operatedAircraftModel, Tu-22M]
-
A.
Tupolev Tu-22 bomber
chosen
The Tupolev Tu-22 is a Soviet-era supersonic long-range bomber designed during the Cold War for high-speed strike missions against strategic targets.
-
B.
Su-22
The Su-22 is a Soviet-designed variable-sweep wing fighter-bomber widely exported and used for ground-attack missions by several air forces, including Poland’s.
-
C.
Sukhoi Su-25
The Sukhoi Su-25 is a Soviet-era, twin-engine, subsonic close air support aircraft designed for attacking ground targets in frontline combat.
-
D.
Tu-128
The Tu-128 was a large, long-range Soviet interceptor aircraft developed during the Cold War to defend the USSR’s vast northern frontiers against strategic bombers.
-
E.
Sukhoi Su-24
The Sukhoi Su-24 is a Soviet-era twin-engine, all-weather supersonic tactical bomber designed for low-level penetration and precision strike missions.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0ea0ae4819096f17d74072b0b78 |
completed | March 7, 2026, 8:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f3434088190b20889c4e68a9361 |
completed | March 12, 2026, 12:56 a.m. |
Created at: March 6, 2026, 10:11 p.m.