Triple
T28953606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-3.10 |
E731088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO information operations doctrine |
C23750
|
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 information operations doctrine Context triple: [AJP-3.10, instanceOf, NATO information operations doctrine]
-
A.
NATO doctrine publication
A NATO doctrine publication is an official document that codifies agreed multinational principles, procedures, and guidance for planning and conducting allied military operations.
-
B.
NATO doctrinal publication
A NATO doctrinal publication is an official, collaboratively developed document that codifies agreed principles, procedures, and guidance for planning and conducting Alliance military operations and activities.
-
C.
NATO Allied Joint Publication
chosen
A NATO Allied Joint Publication is an official doctrinal document that provides standardized guidance and procedures for planning, conducting, and supporting joint and combined military operations among NATO member nations.
-
D.
NATO policy document
A NATO policy document is an official, consensus-based text that articulates the Alliance’s agreed principles, objectives, and guidelines for action on specific security and defense issues.
-
E.
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.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 8:45 a.m.