Triple
T22699030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q‑Series |
E561262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variant of De Havilland Canada Dash 8 |
C46720
|
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: variant of De Havilland Canada Dash 8 Context triple: [Q‑Series, instanceOf, variant of De Havilland Canada Dash 8]
-
A.
Beechcraft Baron variant
A Beechcraft Baron variant is a specific model or configuration within the Baron family of twin‑engine light aircraft, distinguished by particular performance, equipment, or design features.
-
B.
Hawker 800 variant
The Hawker 800 variant is a mid-size business jet model within the Hawker 800 series, distinguished by specific performance, avionics, or interior configuration differences tailored to particular operational or customer requirements.
-
C.
DC-9 family derivative
A DC-9 family derivative is an aircraft model developed from the original McDonnell Douglas DC-9 design, incorporating modifications such as updated engines, avionics, fuselage length, or performance enhancements while retaining the core DC-9 airframe lineage.
-
D.
Tupolev Tu-204 variant
A Tupolev Tu-204 variant is a specific model within the Tu-204 family of Russian twin-engine, medium-range jet airliners, distinguished by modifications in configuration, performance, or role (such as cargo, extended range, or updated avionics).
-
E.
Boeing 737 family variant
A Boeing 737 family variant is a specific model within the 737 series that shares the core narrow-body design but differs in dimensions, performance, capacity, and systems to meet particular airline and route requirements.
- F. None of above. chosen
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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:15 p.m.