Triple
T9959426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Allied Tactical Publications |
E195528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO standardization publication |
C23748
|
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 standardization publication Context triple: [NATO Allied Tactical Publications, instanceOf, NATO standardization publication]
-
A.
NATO Allied Joint Publication
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.
-
B.
NATO doctrinal publication
chosen
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 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.
-
D.
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.
-
E.
ISO/IEC standard
An ISO/IEC standard is a formally agreed-upon specification developed jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) that defines common requirements, guidelines, or characteristics for products, services, or systems to ensure quality, safety, interoperability, and consistency across international markets.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:46 p.m.