Triple
T17808415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell 525 Relentless |
E444630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | super‑medium helicopter |
C39170
|
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: super‑medium helicopter Context triple: [Bell 525 Relentless, instanceOf, super‑medium helicopter]
-
A.
medium‑sized helicopter
A medium-sized helicopter is a rotary-wing aircraft designed to carry a moderate number of passengers or cargo with balanced range, speed, and lifting capacity for roles such as transport, search and rescue, and utility missions.
-
B.
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.
-
C.
heavy-lift helicopter
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.
-
D.
medium utility helicopter
A medium utility helicopter is a versatile, mid-sized rotary-wing aircraft designed to perform a wide range of missions such as troop transport, cargo lift, medical evacuation, and general support operations.
-
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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:14 a.m.