Triple

T13637278
Position Surface form Disambiguated ID Type / Status
Subject U.S. Army Department of the Columbia E325881 entity
Predicate instanceOf P0 FINISHED
Object United States Army department C1992 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: United States Army department
Context triple: [U.S. Army Department of the Columbia, instanceOf, United States Army department]
  • A. United States Army command chosen
    The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense objectives.
  • B. U.S. Army institution
    The U.S. Army institution is the formal organizational structure, culture, and governing framework that defines, supports, and regulates the United States Army’s missions, personnel, doctrine, and operations.
  • C. branch of the United States Army
    A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
  • D. component of the United States Army
    A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
  • E. U.S. Army organizational element
    A U.S. Army organizational element is a structured unit of soldiers, equipment, and command relationships designed to perform specific missions within the Army’s overall force hierarchy.
  • 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_69d8076beddc8190a53156f5bea77f5e completed April 9, 2026, 8:09 p.m.
Created at: April 9, 2026, 9:51 p.m.