Triple

T31120117
Position Surface form Disambiguated ID Type / Status
Subject Minnesota congressional delegation E793198 entity
Predicate canVoteOnFederalLaws P1084 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: [Minnesota congressional delegation, canVoteOnFederalLaws, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canVoteOnFederalLaws
Context triple: [Minnesota congressional delegation, canVoteOnFederalLaws, yes]
  • A. hasElectoralRight
    Indicates that an entity possesses the legal right to participate in elections, typically by voting or standing as a candidate.
  • B. canVoteOnTreaties
    Indicates that an entity has the legal authority or eligibility to participate in voting on treaties.
  • C. canVoteIn
    Indicates that one entity has the legal right or eligibility to participate as a voter in an election or decision-making process associated with another entity.
  • D. hasFederalElectorate
    Indicates that an entity is associated with a specific federal electoral district that represents it in a national legislative body.
  • E. canVoteOn chosen
    Indicates that an entity has the right or permission to participate in a decision-making process by casting a vote on a specific item, issue, or proposal.
  • 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_69f224d0a7688190af3fe3e6e26d01ed completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69c234d648190a243fb2b107136a9 completed May 3, 2026, 12:51 a.m.
PD Predicate disambiguation batch_69f69665cd9c819088c388fc82fec42e completed May 3, 2026, 12:27 a.m.
Created at: April 29, 2026, 9:04 p.m.