Triple
T35962031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukhoi PT-14 |
E1040023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military aircraft project |
C61730
|
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 project Context triple: [Sukhoi PT-14, instanceOf, Soviet military aircraft project]
-
A.
military aircraft project
chosen
A military aircraft project is an organized effort to design, develop, test, and produce an aircraft intended for defense or combat roles, encompassing technical, logistical, financial, and strategic considerations.
-
B.
Soviet aircraft
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.
Cold War military project
A Cold War military project is a government-sponsored initiative focused on developing, testing, or deploying military technologies, strategies, or infrastructure aimed at gaining strategic advantage or deterrence during the geopolitical rivalry between the United States and the Soviet Union.
-
D.
unbuilt aircraft project
An unbuilt aircraft project is a conceptual or proposed airplane design that was planned and possibly studied or partially developed but never constructed or flown.
-
E.
military project
A military project is a coordinated, goal-driven initiative undertaken by armed forces or defense organizations to develop, test, or deploy capabilities, technologies, or operations that enhance national security and military effectiveness.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.