Triple

T30544988
Position Surface form Disambiguated ID Type / Status
Subject EUMC E777387 entity
Predicate instanceOf P0 FINISHED
Object European Union military body C56102 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: European Union military body
Context triple: [EUMC, instanceOf, European Union military body]
  • A. European Union body
    A European Union body is an institution, agency, or other organizational entity established by the EU’s founding treaties or secondary legislation to perform specific political, regulatory, advisory, or administrative functions within the Union’s governance framework.
  • B. European Union military headquarters chosen
    A European Union military headquarters is a central command facility responsible for planning, coordinating, and directing the EU’s joint military operations and defense activities across member states.
  • C. European intergovernmental organization
    A European intergovernmental organization is a cooperative institution formed by European states through treaties to coordinate policies, manage shared interests, and address cross-border issues while preserving national sovereignty.
  • D. European organisation
    A European organisation is an entity based in or primarily serving Europe that coordinates activities, policies, or services across multiple European countries or within a specific European nation.
  • E. Warsaw Pact body
    A Warsaw Pact body is an organizational entity, such as a committee, command structure, or coordinating institution, established under the Warsaw Pact to manage its military, political, or administrative functions among member states.
  • 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_69f2249d183c8190b79937c1768d2163 completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 8:19 p.m.