Triple
T1707408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO military doctrine |
E36901
|
entity |
| Predicate | isDocumentedIn |
P519
|
FINISHED |
| Object |
AJP-3.10 Allied Joint Doctrine for Information Operations
AJP-3.10 Allied Joint Doctrine for Information Operations is a NATO publication that provides overarching principles, guidance, and procedures for planning and conducting information operations in allied joint military campaigns.
|
E192367
|
NE FINISHED |
How this triple was built (4 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: AJP-3.10 Allied Joint Doctrine for Information Operations | Statement: [NATO military doctrine, isDocumentedIn, AJP-3.10 Allied Joint Doctrine for Information Operations]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: AJP-3.10 Allied Joint Doctrine for Information Operations Context triple: [NATO military doctrine, isDocumentedIn, AJP-3.10 Allied Joint Doctrine for Information Operations]
-
A.
Joint Operation Planning and Execution System
The Joint Operation Planning and Execution System (JOPES) is the U.S. Department of Defense’s primary system for integrating and managing joint military planning and execution across combatant commands and services.
-
B.
Battle Management Command, Control and Communications
Battle Management Command, Control and Communications is a U.S. Space Force component focused on integrating and directing space operations through advanced command, control, and communications systems.
-
C.
Soviet deep operations doctrine
Soviet deep operations doctrine was a World War II–era Red Army operational concept that emphasized large-scale, coordinated offensives designed to penetrate enemy defenses in depth and rapidly exploit breakthroughs with mobile forces.
-
D.
U.S. Army/Marine Corps Counterinsurgency Field Manual (FM 3-24)
The U.S. Army/Marine Corps Counterinsurgency Field Manual (FM 3-24) is a doctrinal guide that reshaped modern U.S. military strategy by outlining principles and practices for conducting counterinsurgency operations.
-
E.
Joint Interoperability Test Command
The Joint Interoperability Test Command is a U.S. military organization responsible for testing and certifying the interoperability of defense communications and information systems.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: AJP-3.10 Allied Joint Doctrine for Information Operations Triple: [NATO military doctrine, isDocumentedIn, AJP-3.10 Allied Joint Doctrine for Information Operations]
Generated description
AJP-3.10 Allied Joint Doctrine for Information Operations is a NATO publication that provides overarching principles, guidance, and procedures for planning and conducting information operations in allied joint military campaigns.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: AJP-3.10 Allied Joint Doctrine for Information Operations Target entity description: AJP-3.10 Allied Joint Doctrine for Information Operations is a NATO publication that provides overarching principles, guidance, and procedures for planning and conducting information operations in allied joint military campaigns.
-
A.
Joint Operation Planning and Execution System
The Joint Operation Planning and Execution System (JOPES) is the U.S. Department of Defense’s primary system for integrating and managing joint military planning and execution across combatant commands and services.
-
B.
Battle Management Command, Control and Communications
Battle Management Command, Control and Communications is a U.S. Space Force component focused on integrating and directing space operations through advanced command, control, and communications systems.
-
C.
Soviet deep operations doctrine
Soviet deep operations doctrine was a World War II–era Red Army operational concept that emphasized large-scale, coordinated offensives designed to penetrate enemy defenses in depth and rapidly exploit breakthroughs with mobile forces.
-
D.
U.S. Army/Marine Corps Counterinsurgency Field Manual (FM 3-24)
The U.S. Army/Marine Corps Counterinsurgency Field Manual (FM 3-24) is a doctrinal guide that reshaped modern U.S. military strategy by outlining principles and practices for conducting counterinsurgency operations.
-
E.
Joint Interoperability Test Command
The Joint Interoperability Test Command is a U.S. military organization responsible for testing and certifying the interoperability of defense communications and information systems.
- F. None of above. chosen
Provenance (5 batches)
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. |
| NER | Named-entity recognition | batch_69aa62f6fc9c8190b61cc9872cc2adc0 |
completed | March 6, 2026, 5:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad8ad849648190b2bb0e2a50cd6c75 |
completed | March 8, 2026, 2:42 p.m. |
| NEDg | Description generation | batch_69ad957778a0819080f7fee35f5d8ed5 |
completed | March 8, 2026, 3:27 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ad97aa308c81909f245a2133fc471b |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 4, 2026, 7:30 p.m.