Triple
T10825231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aérospatiale AS 365 Dauphin |
E255481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medium-weight helicopter |
C13997
|
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: medium-weight helicopter Context triple: [Aérospatiale AS 365 Dauphin, instanceOf, medium-weight helicopter]
-
A.
medium‑sized helicopter
chosen
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.
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.
-
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.
military helicopter
A military helicopter is a rotary-wing aircraft designed and equipped for combat, transport, reconnaissance, and support missions in military 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.
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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.