Triple
T13270960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiley Post’s Winnie Mae |
E316053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lockheed Vega |
C32751
|
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: Lockheed Vega Context triple: [Wiley Post’s Winnie Mae, instanceOf, Lockheed Vega]
-
A.
Tupolev ANT-20
The Tupolev ANT-20 was a massive Soviet eight-engine propaganda and transport aircraft of the 1930s, designed to showcase technological prowess and serve as a flying agitprop platform.
-
B.
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.
-
C.
de Havilland Mosquito variant
A de Havilland Mosquito variant is a specific model of the twin‑engine, multi‑role World War II aircraft distinguished by particular modifications to its structure, equipment, or mission profile (such as fighter, bomber, reconnaissance, or night fighter roles).
-
D.
Boulton Paul Defiant variant
A Boulton Paul Defiant variant is any modified version of the British WWII turret-armed fighter aircraft, differing from the base model in aspects such as armament, role, equipment, or structural configuration.
-
E.
Supermarine Swift variant
A Supermarine Swift variant is a specific model within the Supermarine Swift family of British jet fighter and reconnaissance aircraft, distinguished by particular modifications in design, equipment, or role.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:26 p.m.