Triple
T29561169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western military districts of the Russian Empire |
E750042
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military district system |
C13035
|
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: military district system Context triple: [Western military districts of the Russian Empire, instanceOf, military district system]
-
A.
military administrative division
chosen
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
B.
military system
A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
-
C.
militia system
A militia system is a framework in which civilian citizens are organized, trained, and mobilized as a part-time military force for local or national defense, typically supplementing or replacing a standing professional army.
-
D.
military district of the Holy Roman Empire
A military district of the Holy Roman Empire was an administrative and territorial unit organized primarily for defense and military command, grouping various imperial estates under a regional military structure.
-
E.
military structure
A military structure is an organized framework of ranks, units, and command relationships that defines how armed forces are arranged, governed, and coordinated to conduct operations.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:20 p.m.