Triple
T35293511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plant No. 126 Komsomolsk-on-Amur |
E1019292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet defense industry enterprise |
C5343
|
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 defense industry enterprise Context triple: [Plant No. 126 Komsomolsk-on-Amur, instanceOf, Soviet defense industry enterprise]
-
A.
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.
-
B.
Soviet military equipment
Soviet military equipment encompasses the weapons, vehicles, and support systems designed and produced by the Soviet Union to equip its armed forces, characterized by rugged construction, mass production, and doctrinal emphasis on large-scale, combined-arms warfare.
-
C.
Soviet technology
Soviet technology encompasses the industrial, military, and scientific tools, systems, and innovations developed in the USSR, often characterized by rugged simplicity, mass production, and strategic focus over consumer comfort.
-
D.
defense company
chosen
A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
-
E.
defense industry holding company
A defense industry holding company is a corporate entity that owns and manages a portfolio of businesses involved in the research, development, production, and support of military and security-related products and services.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.