Triple
T15938445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukhoi Su-30MKM |
E386498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Su-30 variant |
C36713
|
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: Su-30 variant Context triple: [Sukhoi Su-30MKM, instanceOf, Su-30 variant]
-
A.
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.
-
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.
F-16 Fighting Falcon variant
A specific model or configuration of the F-16 Fighting Falcon multirole fighter aircraft, distinguished by particular avionics, structural features, performance characteristics, or mission capabilities.
-
D.
Dassault Mirage III variant
A Dassault Mirage III variant is a specific model within the Mirage III family of French supersonic jet fighters, distinguished by tailored modifications in avionics, engines, armament, or mission role to meet particular operational or export requirements.
-
E.
Learjet 35 variant
A Learjet 35 variant is a specific model or modification of the Learjet 35 light business jet, distinguished by changes in performance, configuration, or equipment to suit particular operational roles or customer requirements.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:53 a.m.