Triple

T19345168
Position Surface form Disambiguated ID Type / Status
Subject United States Senate seat from Kansas E483856 entity
Predicate subjectToImpeachmentVote P135500 FINISHED
Object yes 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: yes | Statement: [United States Senate seat from Kansas, subjectToImpeachmentVote, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subjectToImpeachmentVote
Context triple: [United States Senate seat from Kansas, subjectToImpeachmentVote, yes]
  • A. impeachmentInitiation
    Indicates the formal start of a process to charge and potentially remove a public official from office for alleged misconduct.
  • B. canImpeach
    Indicates that one entity has the authority or power to formally impeach another entity.
  • C. impeachmentGrounds
    Indicates that a particular reason, action, or circumstance serves as a valid basis or justification for initiating impeachment proceedings against an officeholder.
  • D. impeached
    Indicates that a formal charge of misconduct has been brought against a public official through an official legislative or judicial process.
  • E. impeachedIn
    Indicates that a person has been formally charged with misconduct through an impeachment process in a specified jurisdiction or legislative body.
  • F. None of above. chosen

Provenance (4 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_69d8e8d244f8819080eb1f3491300db2 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e6185a56b4819089336564959b84df completed April 20, 2026, 12:13 p.m.
PD Predicate disambiguation batch_69e4dd12303c8190a2027c062b2dff40 completed April 19, 2026, 1:48 p.m.
PDg Predicate description generation batch_69e4df51ac6c819091ce72b07790ffa6 completed April 19, 2026, 1:57 p.m.
Created at: April 10, 2026, 1:34 p.m.