Triple
T22480877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tu-204C freighter |
E555759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tupolev Tu-204 variant |
C46363
|
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: Tupolev Tu-204 variant Context triple: [Tu-204C freighter, instanceOf, Tupolev Tu-204 variant]
-
A.
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.
-
B.
Airbus A320-214
The Airbus A320-214 is a twin-engine, narrow-body commercial jet airliner designed for short- to medium-haul routes, known for its fuel efficiency, advanced fly-by-wire controls, and widespread use by airlines worldwide.
-
C.
Airbus A330-203
The Airbus A330-203 is a wide-body, twin-engine, long-range commercial airliner variant of the A330 family, optimized for medium to long-haul passenger operations with enhanced range and payload capabilities.
-
D.
Learjet 35 variant
A Learjet 35 variant is a specific model or modification of the Learjet 35 light business jet, distinguished by changes in performance, configuration, or equipment to suit particular operational roles or customer requirements.
-
E.
Airbus A310 variant
The Airbus A310 variant is a wide-body, twin-engine jet airliner derived from the A300 family, featuring a shortened fuselage and improved efficiency for medium- to long-haul routes.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:49 p.m.