Triple
T10879706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Directorate of Communications |
E256889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military body |
C16774
|
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 body Context triple: [Main Directorate of Communications, instanceOf, Soviet military body]
-
A.
branch of the Soviet Armed Forces
A branch of the Soviet Armed Forces is a major organizational component responsible for a specific domain of military operations—such as ground, naval, air, or strategic missile forces—within the overall Soviet military structure.
-
B.
Soviet organization
chosen
A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
-
C.
branch of the Armed Forces of the Russian Federation
A branch of the Armed Forces of the Russian Federation is a major organizational component, such as the Ground Forces, Navy, or Aerospace Forces, with specialized roles, capabilities, and structures for conducting military operations.
-
D.
communist military organization
A communist military organization is an armed group structured under communist ideology, aiming to defend, expand, or enforce a socialist or communist political system through organized military means.
-
E.
Warsaw Pact body
A Warsaw Pact body is an organizational entity, such as a committee, command structure, or coordinating institution, established under the Warsaw Pact to manage its military, political, or administrative functions among member states.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:21 p.m.