Triple

T4583610
Position Surface form Disambiguated ID Type / Status
Subject British Army administrative commands E101913 entity
Predicate instanceOf P0 FINISHED
Object British Army organizational structure C1740 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 organizational structure
Context triple: [British Army administrative commands, instanceOf, British Army organizational structure]
  • A. British Army organizational element chosen
    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. British Army deployment
    British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
  • C. 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.
  • 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. Canadian Army formation
    A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
  • 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_69bd43d4ce208190b53158c882b222e3 completed March 20, 2026, 12:55 p.m.
Created at: March 20, 2026, 1:10 p.m.