Triple
T31817408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McDonnell Douglas KC-10 Extender |
E812173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | jet airliner derivative |
C6011
|
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: jet airliner derivative Context triple: [McDonnell Douglas KC-10 Extender, instanceOf, jet airliner derivative]
-
A.
jet airliner
chosen
A jet airliner is a large, powered aircraft designed to transport passengers and cargo over medium to long distances using jet engines for high-speed, high-altitude flight.
-
B.
Boeing 707 derivative
A Boeing 707 derivative is any aircraft model developed from the original Boeing 707 airframe, incorporating modifications such as structural changes, updated systems, or specialized configurations while retaining its core design lineage.
-
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.
stretched airliner variant
A stretched airliner variant is a lengthened version of an existing aircraft model, typically achieved by adding fuselage sections to increase passenger or cargo capacity while retaining most of the original design and systems.
-
E.
transport aircraft variant
A transport aircraft variant is a specific version of a transport airplane modified or configured for particular cargo, passenger, or mission requirements while retaining the core design of its base model.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:45 p.m.