Triple
T16295668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TriStar K1 |
E395639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lockheed L-1011 TriStar variant |
C37233
|
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: Lockheed L-1011 TriStar variant Context triple: [TriStar K1, instanceOf, Lockheed L-1011 TriStar variant]
-
A.
Hawker Siddeley Trident variant
A Hawker Siddeley Trident variant is a specific model within the Trident family of British-built, three-engined jet airliners, distinguished by particular design modifications, performance characteristics, and operational roles.
-
B.
Boeing 747 variant
A Boeing 747 variant is a specific model or configuration of the Boeing 747 airliner, distinguished by differences in size, range, engines, avionics, or interior layout tailored to particular airline or mission requirements.
-
C.
Boeing 767-223ER
The Boeing 767-223ER is a long-range, wide-body, twin-engine jet airliner variant of the 767-200 series, designed for extended-range commercial passenger service.
-
D.
Boeing 767-200ER
The Boeing 767-200ER is a long-range, wide-body twin-engine jet airliner designed for extended transcontinental and intercontinental routes, offering increased fuel capacity and range over the original 767-200.
-
E.
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.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:06 a.m.