British Administration in the Punjab from 1849-53; Structural Changes and Development
Bibliographic record
Abstract
In 1849, when the British annexed Punjab to the British Empire, they paid attention to the Administration of Punjab. Punjab was a big state that included the areas from the Sutlej to the Indus River. The land was fertile and the people were economically strong. Apart from this, there were some difficulties like the fact that Punjab was located on the North-Western frontier. Due to this, Lord Dalhousie paid special attention to the administration of Punjab and he established a good administration in Punjab during his early years. Under this, a three-man Board of Administration was established, the members of which were Sir Henry Lawrence, John Lawrence and Charles Mansell. Henry Lawrence had been living in Punjab since 1846 CE. Due to this, he had good knowledge of the people of Punjab and was also popular among many of the chieftains of Punjab. But his relations with Lord Dalhousie were not very good. Therefore, Lord Dalhousie did not give him all the power of the Board of Administration. He was given all the rights related to politics. John Lawrence was the brother of Henry Lawrence but he was a supporter of Lord Dalhousie. Therefore, all the financial rights were given to him. Charles Mansell was given judicial rights. In this way, all the power of the Board of Administration was divided among the three members. As a result, he soon brought the people of Punjab under the British Empire. In this paper, I will mention the initial administrative policy of the British in Punjab.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.006 |
| Science and technology studies | 0.009 | 0.003 |
| Scholarly communication | 0.005 | 0.002 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.014 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".