Triple
T23283107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilatus PC-21 |
E588919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | turboprop military trainer aircraft |
C4954
|
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: turboprop military trainer aircraft Context triple: [Pilatus PC-21, instanceOf, turboprop military trainer aircraft]
-
A.
turboprop aircraft
chosen
A turboprop aircraft is a fixed-wing airplane powered by one or more gas-turbine engines that drive propellers to provide efficient thrust at low to medium flight speeds.
-
B.
military trainer aircraft variant
A military trainer aircraft variant is a modified version of a standard military aircraft specifically adapted with dual controls, simplified systems, or performance changes to safely train pilots and aircrew in operational flying skills.
-
C.
jet trainer aircraft
A jet trainer aircraft is a small, high-performance jet-powered airplane designed to train pilots in advanced flying skills, including high-speed handling, navigation, and combat or tactical maneuvers, before they transition to frontline operational aircraft.
-
D.
twin‑engine turboprop regional airliner
A twin-engine turboprop regional airliner is a short- to medium-range passenger aircraft powered by two propeller-driven turbine engines, optimized for efficient, reliable service on regional routes with relatively short runways.
-
E.
twin‑engine aircraft
A twin-engine aircraft is an airplane equipped with two engines, typically mounted on the wings or fuselage, providing increased power, redundancy, and safety compared to single-engine designs.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 4:58 p.m.