Triple

T10125417
Position Surface form Disambiguated ID Type / Status
Subject Army Council E226202 entity
Predicate instanceOf P0 FINISHED
Object British Army administrative body C18742 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 Army administrative body
Context triple: [Army Council, instanceOf, British Army administrative body]
  • A. 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.
  • B. component of British Armed Forces
    A component of the British Armed Forces is an organizational subdivision, such as a service branch or specialized unit, that contributes distinct capabilities and functions to the United Kingdom’s overall military structure and operations.
  • C. 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.
  • D. British military office chosen
    A British military office is an administrative and command center within the United Kingdom’s armed forces where military personnel coordinate operations, manage logistics, and handle official defense-related documentation and communications.
  • E. British Indian administrative body
    A British Indian administrative body is a colonial-era governing institution established by the British in India to manage political, legal, and economic affairs on behalf of the imperial government.
  • 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_69ca843057b48190a86730167f5d6b98 completed March 30, 2026, 2:09 p.m.
Created at: March 30, 2026, 9:05 p.m.