Triple
T9936562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASA C-212 Aviocar |
E193973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | twin-turboprop utility transport 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: twin-turboprop utility transport aircraft Context triple: [CASA C-212 Aviocar, instanceOf, twin-turboprop utility transport aircraft]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
twin-boom aircraft
A twin-boom aircraft is an airplane whose tail assembly is supported by two longitudinal structures (booms) extending rearward from the wings or fuselage, typically joined at the tail by a horizontal stabilizer.
-
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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:44 p.m.