Triple

T3448227
Position Surface form Disambiguated ID Type / Status
Subject Bengal European Regiment E72727 entity
Predicate instanceOf P0 FINISHED
Object British East India Company regiment C12747 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 East India Company regiment
Context triple: [Bengal European Regiment, instanceOf, British East India Company regiment]
  • A. organ of the British East India Company
    An organ of the British East India Company is any official body, office, or instrument through which the Company exercised its administrative, commercial, or political functions.
  • B. British Army organizational element
    A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
  • C. office in the Maratha Empire
    An office in the Maratha Empire was an administrative or military position within the Maratha governance structure, responsible for managing specific territorial, fiscal, or command duties under the authority of the Maratha rulers.
  • D. British Army facility
    A British Army facility is a location owned, operated, or used by the British Army for purposes such as training, administration, logistics, accommodation, storage, or operational deployment.
  • E. British Army position
    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.
  • F. None of above. chosen

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_69ad85b05c848190b7a28ceec2bd7b74 completed March 8, 2026, 2:20 p.m.
Created at: March 8, 2026, 3:16 p.m.