Triple
T25458168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mil Mi-10K |
E637968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variant of Mil Mi-10 |
C50208
|
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: variant of Mil Mi-10 Context triple: [Mil Mi-10K, instanceOf, variant of Mil Mi-10]
-
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.
variant of Kawasaki C-1
A variant of the Kawasaki C-1 is a modified version of the Japanese twin‑engine military transport aircraft, adapted with specific structural, avionics, or role-based changes to meet particular operational requirements.
-
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.
multi‑purpose helicopter
A multi-purpose helicopter is a versatile rotary-wing aircraft designed to perform a wide range of missions—such as transport, search and rescue, surveillance, and support—by accommodating different payloads, equipment, and operating conditions.
-
E.
twin-engine helicopter
A twin-engine helicopter is a rotary-wing aircraft equipped with two independent engines that provide increased power, redundancy, and safety for missions such as transport, search and rescue, and offshore operations.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:10 p.m.