Triple
T1829813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU Member States armed forces |
E40735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence capability pool |
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: defence capability pool Context triple: [EU Member States armed forces, instanceOf, defence capability pool]
-
A.
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.
-
B.
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.
-
C.
integrated air defence system
An integrated air defence system is a coordinated network of sensors, command and control elements, and weapon systems designed to detect, track, and engage aerial threats to protect designated airspace and assets.
-
D.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
E.
missile defense program
A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended targets.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.