Triple
T30850575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737-500 |
E785767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boeing 737 Classic variant |
C46359
|
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 737 Classic variant Context triple: [Boeing 737-500, instanceOf, Boeing 737 Classic variant]
-
A.
Boeing 737 family variant
chosen
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.
-
B.
Boeing 757-200
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.
-
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.
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.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:46 p.m.