Triple
T36058808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 777-200ER |
E1043019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boeing 777 variant |
C33075
|
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 777 variant Context triple: [Boeing 777-200ER, instanceOf, Boeing 777 variant]
-
A.
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.
-
B.
Boeing 777-200ER
chosen
The Boeing 777-200ER is a long-range, wide-body twin-engine jet airliner designed for extended operations on intercontinental routes, offering high passenger capacity and fuel efficiency.
-
C.
Boeing 737 family variant
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.
-
D.
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.
-
E.
Boeing 767-300ER
The Boeing 767-300ER is a long-range, wide-body twin-engine jet airliner designed for efficient medium- to long-haul passenger and cargo operations.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:08 p.m.