Triple
T16596757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspectorate of Infantry of the Russian Empire |
E403227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | central military authority |
C34262
|
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 authority Context triple: [Inspectorate of Infantry of the Russian Empire, instanceOf, central military authority]
-
A.
military-technical authority
A military-technical authority is an entity or individual empowered to make decisions and provide expert guidance on the development, deployment, and regulation of military technologies and related operational capabilities.
-
B.
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.
-
C.
central governmental authority
A central governmental authority is the primary governing body that holds ultimate decision-making power and administrative control over a state or political system.
-
D.
military establishment
chosen
A military establishment is an organized institution or network of institutions responsible for a nation's armed forces, defense policies, and related political, economic, and social interests.
-
E.
nuclear command authority
Nuclear command authority is the centralized system of legal, political, and military structures and procedures that control the authorization, decision-making, and execution of a state’s nuclear weapons use.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:16 a.m.