Triple
T6803214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-16V Viper upgrade |
E156236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | F-16 Fighting Falcon variant |
C21661
|
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: F-16 Fighting Falcon variant Context triple: [F-16V Viper upgrade, instanceOf, F-16 Fighting Falcon variant]
-
A.
F-4 Phantom II variant
A specific model or modification of the McDonnell Douglas F-4 Phantom II fighter-bomber, distinguished by particular avionics, structural changes, or mission equipment tailored to specific operational roles or users.
-
B.
Panavia Tornado variant
A Panavia Tornado variant is a specific model of the multirole combat aircraft tailored with distinct avionics, structural modifications, and mission equipment to fulfill specialized roles such as strike, reconnaissance, or air defense.
-
C.
variant of Lockheed Martin F-35 Lightning II
A variant of the Lockheed Martin F-35 Lightning II is a specific configuration of the fifth-generation multirole stealth fighter tailored to distinct mission profiles, service branches, or export requirements while retaining the core airframe, avionics, and low-observable characteristics.
-
D.
X-plane
An X-plane is an experimental aircraft designed to test and demonstrate new aviation technologies, configurations, or performance capabilities beyond those of conventional aircraft.
-
E.
single‑engine fighter aircraft
A single-engine fighter aircraft is a fast, maneuverable military airplane powered by one engine and designed primarily for air-to-air combat and limited ground-attack missions.
- F. None of above. chosen
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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:16 p.m.