Triple
T11888781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-444 |
E282860
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tupolev aircraft |
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: Tupolev aircraft Context triple: [Tupolev Tu-444, instanceOf, Tupolev aircraft]
-
A.
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.
-
B.
Soviet design bureau
A Soviet design bureau was a state-controlled, specialized engineering and research organization responsible for conceiving, developing, and prototyping advanced military and industrial technologies within the centrally planned Soviet system.
-
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.
rocket design bureau
A rocket design bureau is an organization that specializes in the research, engineering, and development of rocket systems and related aerospace technologies.
-
E.
component of the Soviet Air Forces
A component of the Soviet Air Forces is an organizational unit, formation, or specialized element (such as a regiment, division, or support service) that collectively contributed to the operational, logistical, and strategic capabilities of the USSR’s military aviation.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.