Triple
T20491606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KB-50 |
E502758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variant of B-50 Superfortress |
C28565
|
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: variant of B-50 Superfortress Context triple: [KB-50, instanceOf, variant of B-50 Superfortress]
-
A.
Lockheed Constellation variant
A Lockheed Constellation variant is a specific model within the Constellation family of four‑engined, propeller‑driven airliners and military transports, distinguished by particular structural, performance, or role-related modifications.
-
B.
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.
-
C.
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.
-
D.
bomber aircraft variant
chosen
A bomber aircraft variant is a specific version of a bomber designed or modified to perform particular roles, missions, or operate under distinct performance, payload, or technological configurations.
-
E.
jet-powered medium bomber
A jet-powered medium bomber is a military aircraft designed to deliver moderate payloads of bombs or missiles over medium ranges at high subsonic or supersonic speeds, balancing striking power, range, and maneuverability.
- 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_69e0b4b0373881909dd3e9387f82eab4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:35 a.m.