Triple
T22319945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-32A |
E551755
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boeing 757 variant |
C25849
|
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: Boeing 757 variant Context triple: [C-32A, instanceOf, Boeing 757 variant]
-
A.
Boeing 757-200
chosen
The Boeing 757-200 is a narrow-body, twin-engine jet airliner designed for medium- to long-range routes, known for its high performance, fuel efficiency, and versatility in both passenger and cargo configurations.
-
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.
Lockheed L-1011 TriStar variant
A Lockheed L-1011 TriStar variant is a specific model within the L-1011 widebody trijet family distinguished by particular combinations of engine performance, range, structural modifications, and avionics tailored to different airline or mission requirements.
-
D.
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.
-
E.
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.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.