Triple
T31502712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Проект 671 |
E803730
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | советский военный проект |
C9413
|
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: советский военный проект Context triple: [Проект 671, instanceOf, советский военный проект]
-
A.
military project
chosen
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.
-
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.
soviet
Soviet refers to anything related to the former Soviet Union (USSR), including its government, ideology, culture, or people associated with its socialist, one-party state system.
-
E.
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.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:45 p.m.