Triple
T28655153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AS332 L2 |
E725310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Super Puma variant |
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 Puma variant Context triple: [AS332 L2, instanceOf, Super Puma variant]
-
A.
Bell 206 variant
A Bell 206 variant is a specific model within the Bell 206 family of light, twin-blade helicopters that incorporates distinct modifications in design, performance, or equipment to fulfill particular operational roles or requirements.
-
B.
super‑medium helicopter
chosen
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.
Panavia Tornado variant
A Panavia Tornado variant is a specific model of the multirole combat aircraft tailored with distinct avionics, structural modifications, and mission equipment to fulfill specialized roles such as strike, reconnaissance, or air defense.
-
D.
variant of Mil Mi-10
A variant of the Mil Mi-10 is a specialized version of the Soviet heavy-lift helicopter tailored with modified equipment, structure, or performance features to fulfill distinct transport or support roles.
-
E.
Fairey Gannet variant
A Fairey Gannet variant is a specific model or modification of the British carrier-borne, twin-engine, anti-submarine and maritime patrol aircraft distinguished by changes in role, equipment, or structural features.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:54 a.m.