Triple
T32526828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BK117 C-2 |
E831337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | twin‑engine light utility helicopter |
C8273
|
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: twin‑engine light utility helicopter Context triple: [BK117 C-2, instanceOf, twin‑engine light utility helicopter]
-
A.
twin‑engine helicopter
chosen
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.
-
B.
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 transporting passengers or cargo.
-
C.
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.
-
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.
single‑engine helicopter
A single-engine helicopter is a rotary-wing aircraft powered by one main engine that drives the main rotor (and typically a tail rotor) to provide lift, thrust, and control for vertical takeoff, landing, and low-speed maneuvering.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:01 a.m.