Triple
T1707234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logistic Support Command |
E36898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military logistics 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: military logistics command Context triple: [Logistic Support Command, instanceOf, military logistics 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.
United States Army command
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.
-
C.
military communications organization
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
-
D.
United States Army major command
A United States Army major command is a high-level organizational entity responsible for overseeing and directing large-scale Army operations, resources, and support functions within a specific mission area or geographic region.
-
E.
major command of the United States Army
A major command of the United States Army is a high-level organizational entity responsible for overseeing, directing, and supporting large-scale operational, administrative, or functional missions across multiple subordinate units and installations.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.