Triple

T38391248
Position Surface form Disambiguated ID Type / Status
Subject Canadian Forces Administrative Orders E899723 entity
Predicate instanceOf P0 FINISHED
Object Canadian Armed Forces directive C65640 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: Canadian Armed Forces directive
Context triple: [Canadian Forces Administrative Orders, instanceOf, Canadian Armed Forces directive]
  • A. Canadian Armed Forces position
    A Canadian Armed Forces position is a defined role within Canada's military organization that specifies an individual's rank, duties, responsibilities, and placement within the command structure.
  • B. Canadian Armed Forces sub-component
    A Canadian Armed Forces sub-component is a distinct organizational element within the Canadian military structure, such as a specific command, formation, or unit, that performs defined roles and responsibilities in support of national defense objectives.
  • C. United States Army directive
    A United States Army directive is an official, authoritative order or instruction issued by Army leadership that establishes or changes policy, procedures, responsibilities, or standards for the organization.
  • D. members of the Canadian Armed Forces
    Individuals who serve in Canada’s unified military organization, encompassing the Royal Canadian Navy, Canadian Army, and Royal Canadian Air Force, responsible for defending Canada’s sovereignty and contributing to international peace and security.
  • E. Canadian military institution
    A Canadian military institution is an organization established by the Government of Canada to develop, manage, and support the nation’s armed forces through training, policy, operations, and defense-related services.
  • 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_69f76e5c9b808190b486523f5c2f817d completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:31 p.m.