Triple
T17715745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isolation of the Trans-Mississippi Confederacy |
E442194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military logistics problem |
C39585
|
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 problem Context triple: [Isolation of the Trans-Mississippi Confederacy, instanceOf, military logistics problem]
-
A.
military logistics software system
A military logistics software system is an integrated digital platform that plans, tracks, and optimizes the movement, supply, maintenance, and readiness of military resources across operations and theaters.
-
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.
logistics brigade
A logistics brigade is a military unit responsible for planning, coordinating, and executing the supply, transportation, maintenance, and support services needed to sustain combat and support forces.
-
D.
logistics doctrine
Logistics doctrine is the overarching set of principles, policies, and standardized practices that guide how an organization plans, executes, and sustains the movement and support of resources to achieve its operational objectives.
-
E.
coalition logistics framework
A coalition logistics framework is a structured model that coordinates and optimizes the planning, allocation, and movement of resources across multiple allied organizations to achieve shared operational objectives.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:06 a.m.