Triple
T8590112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Defence Union |
E203407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed defence framework |
C4088
|
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: proposed defence framework Context triple: [European Defence Union, instanceOf, proposed defence framework]
-
A.
cryptographic protocol framework
A cryptographic protocol framework is a structured set of tools, abstractions, and rules that enables the design, specification, analysis, and implementation of secure communication protocols.
-
B.
command-and-control framework
A command-and-control framework is a structured system that enables centralized coordination, tasking, and monitoring of distributed agents or components, often used to manage operations, automation, or cyber activities.
-
C.
defensive measure
A defensive measure is an action, system, or strategy designed to protect against, reduce, or mitigate harm from potential threats or attacks.
-
D.
defensive avionics system
A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
-
E.
European Union security and defence policy instrument
chosen
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.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.