Triple

T17307965
Position Surface form Disambiguated ID Type / Status
Subject Adjutant-General in India E420212 entity
Predicate instanceOf P0 FINISHED
Object British Indian Army position C5138 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: British Indian Army position
Context triple: [Adjutant-General in India, instanceOf, British Indian Army position]
  • A. Indian Army position
    An Indian Army position is a specific rank or role within the organizational hierarchy of the Indian Army, defining an individual's authority, responsibilities, and duties in military operations and administration.
  • B. British Army position chosen
    A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
  • C. branch of the British Indian Army
    A branch of the British Indian Army is a major organizational subdivision responsible for a specific type of military function or service, such as infantry, cavalry, artillery, or engineering, within the colonial armed forces of British India.
  • D. Indian Army formation
    An Indian Army formation is an organized military unit or grouping, such as a corps, division, brigade, or battalion, structured for command, control, and execution of land-based operations within the Indian Army.
  • E. British colonial regiment
    A British colonial regiment is a military unit raised, organized, and commanded by the British Empire from its overseas colonies, typically composed of local recruits led by British officers to serve imperial defense and expansion.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
Created at: April 10, 2026, 5:43 a.m.