Triple
T3897415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Joint Ballistics Memorandum of Understanding |
E90402
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military standardization document |
C2034
|
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 standardization document Context triple: [NATO Joint Ballistics Memorandum of Understanding, instanceOf, military standardization document]
-
A.
military standard
A military standard is an officially established set of technical, procedural, or quality requirements used by armed forces to ensure compatibility, reliability, and uniformity of equipment, systems, and practices.
-
B.
standards-related document
chosen
A standards-related document is an authoritative publication that defines, explains, or supports the development, implementation, or interpretation of technical or organizational standards.
-
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.
military planning document
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or activities.
-
E.
Internet standardization document
An Internet standardization document is an authoritative specification that defines technical protocols, formats, or practices to ensure interoperability and consistent behavior across the global Internet.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.