Triple

T35002218
Position Surface form Disambiguated ID Type / Status
Subject British high command in India E1009712 entity
Predicate instanceOf P0 FINISHED
Object British Indian Army command C14725 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 command
Context triple: [British high command in India, instanceOf, British Indian Army command]
  • A. Indian Army command
    Indian Army command is an organizational unit responsible for directing, coordinating, and controlling military operations, administration, and logistics within a defined geographic or functional area of the Indian Army.
  • B. branch of the British Indian Army chosen
    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.
  • C. 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.
  • D. branch of the Indian Army
    A branch of the Indian Army is a major organizational subdivision responsible for specific operational, combat, or support functions within the Army’s overall structure.
  • 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_69f76dcb716881909f75e4fd60ab2284 completed May 3, 2026, 3:46 p.m.
Created at: May 3, 2026, 4:01 p.m.