Triple
T11784005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-29 |
E280223
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Convair 240 variant |
C29809
|
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: Convair 240 variant Context triple: [T-29, instanceOf, Convair 240 variant]
-
A.
Lockheed Model 10 Electra variant
A Lockheed Model 10 Electra variant is a specific configuration of the twin‑engine, all‑metal monoplane airliner distinguished by modifications in equipment, performance, or role (such as transport, survey, or military use) from the standard Model 10 design.
-
B.
Handley Page Halifax variant
A Handley Page Halifax variant is a specific model or modification of the British four‑engined heavy bomber, distinguished by changes in engines, armament, structure, or equipment to fulfill particular operational roles during its service life.
-
C.
McDonnell Douglas aircraft
McDonnell Douglas aircraft are a family of commercial and military airplanes known for their distinctive designs, such as the DC-9/MD-80 series and F-15 fighter, produced by the former American aerospace manufacturer McDonnell Douglas before its merger with Boeing.
-
D.
F-4 Phantom II variant
A specific model or modification of the McDonnell Douglas F-4 Phantom II fighter-bomber, distinguished by particular avionics, structural changes, or mission equipment tailored to specific operational roles or users.
-
E.
Gulfstream V variant
A Gulfstream V variant is a specific model or configuration of the long-range, large-cabin Gulfstream V business jet, modified to meet particular performance, mission, or customer requirements.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.