Triple
T25428665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces Reserve Command |
E637189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reserve forces command |
C50027
|
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: reserve forces command Context triple: [Armed Forces Reserve Command, instanceOf, reserve forces command]
-
A.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
B.
U.S. Army sustainment command
The U.S. Army Sustainment Command is the organization responsible for providing logistics, supply, maintenance, and distribution support to ensure Army forces are equipped and sustained during training, deployment, and combat operations worldwide.
-
C.
standby force
chosen
A standby force is a pre-organized, trained, and readily available group of personnel and resources maintained in reserve for rapid deployment in response to emergencies, crises, or specific operational needs.
-
D.
military police command
A military police command is an organizational unit within the armed forces responsible for law enforcement, security operations, discipline, and order among military personnel and installations.
-
E.
United States military command
The United States military command is the hierarchical structure of authority and control through which national defense policies and military operations are directed, coordinated, and executed across all branches of the U.S. 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:58 p.m.