Triple
T9521301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Strategic Defence and Security Review 2015 |
E229649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence white paper |
C24419
|
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: defence white paper Context triple: [UK Strategic Defence and Security Review 2015, instanceOf, defence white paper]
-
A.
European Union security and defence policy instrument
A European Union security and defence policy instrument is a formal mechanism, tool, or framework established by the EU to plan, coordinate, and implement collective actions in the fields of security, crisis management, and defence.
-
B.
defence estate
A defence estate is the collective portfolio of land, buildings, infrastructure, and facilities owned, leased, or managed by a nation's defence organization to support military operations, training, administration, and logistics.
-
C.
security doctrine
chosen
A security doctrine is a formalized set of principles and strategies that guides how a state or organization understands, prioritizes, and responds to threats to its security.
-
D.
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.
-
E.
written defense
A written defense is a structured, formal document in which an individual systematically justifies, explains, and supports their position, decisions, or work—often in academic, legal, or professional contexts—using evidence, reasoning, and clear argumentation.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:59 p.m.