Triple
T2628395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian General Staff |
E59174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | central military command authority |
C298
|
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: central military command authority Context triple: [Russian General Staff, instanceOf, central military command authority]
-
A.
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.
-
B.
United States Army command
The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense objectives.
-
C.
army commander post
An army commander post is a designated command facility or position from which a military commander directs, coordinates, and controls the operations of assigned forces.
-
D.
major command of the United States Army
A major command of the United States Army is a high-level organizational entity responsible for overseeing, directing, and supporting large-scale operational, administrative, or functional missions across multiple subordinate units and installations.
-
E.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:50 p.m.