Triple
T35348975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavochkin La-190 |
E1020822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military aircraft prototype |
C6658
|
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: Soviet military aircraft prototype Context triple: [Lavochkin La-190, instanceOf, Soviet military aircraft prototype]
-
A.
British military aircraft prototype
A British military aircraft prototype is an experimental or pre-production aircraft developed in the United Kingdom to test and refine new designs, technologies, or capabilities for potential adoption by the armed forces.
-
B.
Soviet aircraft
chosen
Soviet aircraft are military and civilian airplanes and helicopters designed, produced, or operated by the Soviet Union, reflecting its technological, strategic, and industrial priorities from 1922 to 1991.
-
C.
nuclear-powered aircraft prototype
A nuclear-powered aircraft prototype is an experimental aircraft design that uses a nuclear reactor as its primary energy source to generate thrust or power propulsion systems, aiming for extremely long endurance without refueling.
-
D.
Lisunov Li-2 variant
The Lisunov Li-2 variant is a Soviet-licensed and modified version of the Douglas DC-3 airliner, adapted for multiple roles including transport, paratroop deployment, and bombing under varying operational conditions.
-
E.
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.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.