Triple
T23085405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega K-707 tanker |
E575583
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | modified Boeing 707 |
C15324
|
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: modified Boeing 707 Context triple: [Omega K-707 tanker, instanceOf, modified Boeing 707]
-
A.
Boeing 707 derivative
chosen
A Boeing 707 derivative is any aircraft model developed from the original Boeing 707 airframe, incorporating modifications such as structural changes, updated systems, or specialized configurations while retaining its core design lineage.
-
B.
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.
-
C.
Convair 240 variant
A Convair 240 variant is a specific model within the Convair 240 family of twin‑engine, short- to medium-range airliners that incorporates design modifications or performance improvements over the original baseline aircraft.
-
D.
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.
-
E.
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.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:57 p.m.