Triple
T38046146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing T-43 |
E949623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boeing 737 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 variant Context triple: [Boeing T-43, instanceOf, Boeing 737 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 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.
Boeing 707 derivative
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.
-
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.
Beechcraft Baron variant
A Beechcraft Baron variant is a specific model or configuration within the Baron family of twin‑engine light aircraft, distinguished by particular performance, equipment, or design features.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.