Triple
T12833364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stavka of the Red Army |
E306842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supreme military command |
C21094
|
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: supreme military command Context triple: [Stavka of the Red Army, instanceOf, supreme military command]
-
A.
United States military command
The United States military command is the hierarchical structure of authority and control through which national defense policies and military operations are directed, coordinated, and executed across all branches of the U.S. Armed Forces.
-
B.
Commander-in-chief
The Commander-in-chief is the highest-ranking authority responsible for the overall command, strategic direction, and ultimate decision-making of a nation's armed forces.
-
C.
Allied military authority
An Allied military authority is a governing body established by cooperating allied nations' armed forces to administer, control, and coordinate military and sometimes civil affairs in occupied or liberated territories during and immediately after conflict.
-
D.
supreme military rank
A supreme military rank is the highest possible position in a nation's armed forces hierarchy, typically held by a single individual with ultimate authority over all military operations and strategy.
-
E.
military decision-making body
chosen
A military decision-making body is an organized group of authorized personnel responsible for analyzing strategic and tactical information, evaluating options, and issuing binding directives that guide military operations and policy.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:34 p.m.