Triple
T10879450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Logistics Directorate |
E256883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military agency |
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 agency Context triple: [Main Logistics Directorate, instanceOf, Soviet military agency]
-
A.
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.
-
B.
government agency of Russia
A government agency of Russia is an official state body established by the Russian Federation to implement public policy, administer specific functions, and provide services within a defined area of governance under federal or regional authority.
-
C.
Soviet government ministry
A Soviet government ministry was a centralized state administrative body responsible for directing and managing a specific sector of the economy, society, or state functions under the authority of the USSR’s Communist Party leadership.
-
D.
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.
-
E.
Russian federal agency
A Russian federal agency is a government body established by the Russian Federation to implement federal laws, execute state policies, and manage specific administrative functions across the country.
- 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.