Triple
T28879041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-4 |
E732361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military logistics doctrine |
C23998
|
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 doctrine Context triple: [AJP-4, instanceOf, military logistics doctrine]
-
A.
logistics doctrine
chosen
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.
-
B.
military organizational doctrine
Military organizational doctrine is the formalized set of principles, structures, and procedures that guide how armed forces are organized, coordinated, and employed to achieve strategic and operational objectives.
-
C.
logistics doctrine publication
A logistics doctrine publication is an authoritative document that defines the principles, concepts, and standardized procedures guiding the planning, execution, and support of logistics operations within an organization or military force.
-
D.
military logistics directorate
A military logistics directorate is an organizational unit responsible for planning, coordinating, and managing the procurement, storage, movement, and maintenance of supplies, equipment, and services that sustain armed forces operations.
-
E.
military doctrinal framework
A military doctrinal framework is a structured set of principles, concepts, and guidelines that shapes how armed forces plan, organize, and conduct operations across different levels of war.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:41 a.m.