Triple

T12123204
Position Surface form Disambiguated ID Type / Status
Subject European Defence Community plan for German rearmament E288743 entity
Predicate instanceOf P0 FINISHED
Object defence integration plan C30954 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 integration plan
Context triple: [European Defence Community plan for German rearmament, instanceOf, defence integration plan]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. defence procurement position
    A defence procurement position is a role responsible for acquiring military equipment, services, and technologies through managing contracts, suppliers, and compliance with defence regulations and strategic requirements.
  • E. defence staff committee
    A defence staff committee is a formal group of senior military and defence officials convened to coordinate policy, planning, and strategic decision-making for national or organizational security.
  • 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_69d6ab4b5e4c81909950b17151eb0951 completed April 8, 2026, 7:23 p.m.
Created at: April 8, 2026, 9:49 p.m.