Triple
T18795539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prague Summit Declaration |
E459624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO policy document |
C41246
|
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 policy document Context triple: [Prague Summit Declaration, instanceOf, NATO policy document]
-
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
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 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.
-
E.
NATO process
A NATO process is a structured, collaborative decision-making and operational framework used by the North Atlantic Treaty Organization to plan, coordinate, and execute collective defense and security activities among its member states.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.