Triple
T7536923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Services of Supply (U.S. Army) |
E178173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | logistical command |
C2381
|
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: logistical command Context triple: [Services of Supply (U.S. Army), instanceOf, logistical command]
-
A.
logistics command
chosen
Logistics command is the organizational function responsible for planning, coordinating, and controlling the movement, supply, and maintenance of resources to ensure operational readiness and sustained support.
-
B.
logistical operation
A logistical operation is a coordinated set of activities and processes that plan, implement, and control the efficient movement and storage of goods, information, or resources from origin to destination.
-
C.
theatre command
Theatre command is a high-level military headquarters responsible for planning, directing, and coordinating operations across a broad geographic area or theater of war.
-
D.
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.
-
E.
major command echelon
A major command echelon is a high-level organizational tier within a military or large institution that oversees multiple subordinate units and directs strategic operations, resources, and policies across a broad mission area.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:48 p.m.