Triple
T8233994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-01 Allied Joint Doctrine |
E192359
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO doctrine publication |
C23746
|
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: NATO doctrine publication Context triple: [AJP-01 Allied Joint Doctrine, instanceOf, NATO doctrine publication]
-
A.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
-
B.
U.S. Department of Defense strategic document
A U.S. Department of Defense strategic document is an official, high-level publication that outlines long-term defense objectives, priorities, and plans for employing military resources to protect national security interests.
-
C.
United States military manual
A United States military manual is an official publication that provides standardized doctrine, procedures, and guidance for the organization, training, and operations of U.S. armed forces.
-
D.
NATO capability
A NATO capability is a specific military, political, or logistical asset, function, or competence that member states collectively develop, maintain, and coordinate to fulfill the Alliance’s strategic objectives and operational requirements.
-
E.
British Army doctrine publication
A British Army doctrine publication is an official document that articulates the Army’s authoritative principles, concepts, and guidance for the conduct of operations and training.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:46 p.m.