Triple

T3977075
Position Surface form Disambiguated ID Type / Status
Subject Indianization of the officer corps (interwar period) E85668 entity
Predicate instanceOf P0 FINISHED
Object policy of the British Raj C1297 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: policy of the British Raj
Context triple: [Indianization of the officer corps (interwar period), instanceOf, policy of the British Raj]
  • A. presidency of British India
    The presidency of British India was a major administrative division governed by the British East India Company and later the British Crown, serving as a regional center of political, military, and economic control.
  • B. colonial policy chosen
    Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
  • C. Mughal-era legal code
    A Mughal-era legal code is a structured body of laws, regulations, and judicial principles developed under the Mughal Empire that governed civil, criminal, fiscal, and religious matters by blending Islamic jurisprudence with local customs and imperial decrees.
  • D. British colonial position
    A British colonial position is an official role or office established by the British Empire to administer, govern, or oversee territories and populations under colonial rule.
  • E. district of British India
    A district of British India was an administrative subdivision governed by colonial authorities, typically comprising multiple towns and villages, used for managing revenue collection, law and order, and local governance under the British Raj.
  • 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_69aed93908348190a26c8aaf4fab3e86 completed March 9, 2026, 2:29 p.m.
Created at: March 9, 2026, 3:33 p.m.