Triple

T121015
Position Surface form Disambiguated ID Type / Status
Subject Ministerial Conference E2443 entity
Predicate canTakeDecisionsBy P2165 FINISHED
Object voting in exceptional circumstances LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: voting in exceptional circumstances | Statement: [Ministerial Conference, canTakeDecisionsBy, voting in exceptional circumstances]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canTakeDecisionsBy
Context triple: [Ministerial Conference, canTakeDecisionsBy, voting in exceptional circumstances]
  • A. decidesOn
    Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
  • B. decides
    Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
  • C. canBe
    Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
  • D. canEnforce
    Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon another entity.
  • E. decisionType chosen
    Indicates the specific category or nature of a decision associated with an entity or event.
  • F. None of above.

Provenance (3 batches)

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_69a2506c5428819085c28a8884790e29 completed Feb. 28, 2026, 2:18 a.m.
NER Named-entity recognition batch_69a258fd278481908ad4498e03f38e2f completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a25647fe6081908cb0405266d35ff5 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:24 a.m.