Triple

T2132553
Position Surface form Disambiguated ID Type / Status
Subject Council of Ministers of Poland E46573 entity
Predicate canBeSubjectTo P1313 FINISHED
Object vote of no confidence 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: vote of no confidence | Statement: [Council of Ministers of Poland, canBeSubjectTo, vote of no confidence]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeSubjectTo
Context triple: [Council of Ministers of Poland, canBeSubjectTo, vote of no confidence]
  • A. isSubjectTo chosen
    Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
  • B. canBe
    Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
  • C. canBeSuedFor
    Indicates that one party is legally liable or potentially subject to legal action by another party for a specified cause or wrongdoing.
  • D. hasLegalSubject
    Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
  • E. subjectCanBe
    Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
  • 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_69a88a1626548190ae59a5028c3baa8e completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abbb7b13ac819094d43159fff984cf completed March 7, 2026, 5:45 a.m.
PD Predicate disambiguation batch_69abb7bf56e481909b0f497d238451cc completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:44 p.m.