Triple

T10341749
Position Surface form Disambiguated ID Type / Status
Subject Prüm Decisions E243142 entity
Predicate instanceOf P0 FINISHED
Object EU Council decision C14089 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: EU Council decision
Context triple: [Prüm Decisions, instanceOf, EU Council decision]
  • A. Council conclusions of the European Union
    Council conclusions of the European Union are formal, non-legally binding statements adopted by the Council that express the EU member states’ collective political positions, priorities, or intended actions on specific policy issues.
  • B. EU Council formation
    The EU Council formation is a configuration of national ministers from each EU member state, grouped by policy area (e.g., agriculture, finance, environment) to adopt legislation and coordinate policies within that specific domain.
  • C. EU Council committee
    An EU Council committee is a specialized working group composed of representatives from EU member states that prepares, negotiates, and coordinates issues and draft legislation for decision-making by the Council of the European Union.
  • D. European Union convention
    A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
  • E. EU legal act chosen
    An EU legal act is a binding or non-binding instrument adopted by the European Union’s institutions—such as regulations, directives, decisions, recommendations, or opinions—to create, modify, or guide the application of law within the EU legal order.
  • 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_69d381af787481908bc401325c760a88 completed April 6, 2026, 9:49 a.m.
Created at: April 6, 2026, 11:55 a.m.