Triple
T29018838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nord 260 |
E737391
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | twin-turboprop regional airliner prototype |
C15296
|
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 regional airliner prototype Context triple: [Nord 260, instanceOf, twin-turboprop regional airliner prototype]
-
A.
twin‑engine turboprop regional airliner
chosen
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.
turboprop aircraft
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.
-
C.
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.
-
D.
twin-seat aircraft
A twin-seat aircraft is an airplane designed with two seats, typically arranged in tandem or side-by-side, to accommodate a pilot and an additional occupant such as a co-pilot, instructor, or passenger.
-
E.
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.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:47 a.m.