Triple
T35017446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mil Mi-6 |
E1010090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heavy transport helicopter |
C4816
|
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: heavy transport helicopter Context triple: [Mil Mi-6, instanceOf, heavy transport helicopter]
-
A.
heavy-lift helicopter
chosen
A heavy-lift helicopter is a large rotary-wing aircraft designed to transport exceptionally heavy cargo, equipment, or personnel, often in challenging environments and over relatively short distances.
-
B.
super‑medium helicopter
A super‑medium helicopter is a rotorcraft class larger and more capable than medium helicopters, offering extended range, payload, and endurance for missions such as offshore transport, search and rescue, and utility operations while remaining smaller and more economical than heavy-lift helicopters.
-
C.
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.
-
D.
long-range helicopter
A long-range helicopter is a rotary-wing aircraft designed to travel extended distances without refueling, typically featuring increased fuel capacity, efficient engines, and enhanced navigation and comfort systems for sustained operations.
-
E.
military helicopter
A military helicopter is a rotary-wing aircraft designed and equipped for combat, transport, reconnaissance, and support missions in military operations.
- F. None of above.
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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.