Triple
T9866838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McDonnell Douglas MD-80 |
E239854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | twin-engine jet airliner series |
C18627
|
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-engine jet airliner series Context triple: [McDonnell Douglas MD-80, instanceOf, twin-engine jet airliner series]
-
A.
series of jet airliners
chosen
A series of jet airliners is a family of related jet-powered passenger aircraft models that share a common design lineage but differ in size, range, capacity, or performance to serve various airline needs.
-
B.
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.
-
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.
wide-body jet airliner
A wide-body jet airliner is a large passenger aircraft with two aisles and a wide fuselage designed to carry high numbers of passengers or cargo over medium to long-haul routes.
-
E.
narrow-body airliner family
A narrow-body airliner family is a series of closely related single-aisle commercial passenger aircraft sharing a common design platform, systems, and operational characteristics but differing in size, range, and capacity.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:36 p.m.