Triple

T1488273
Position Surface form Disambiguated ID Type / Status
Subject Speaker of the House of Representatives E29517 entity
Predicate mayHavePower P21124 FINISHED
Object to cast tie‑breaking votes in some systems 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: to cast tie‑breaking votes in some systems | Statement: [Speaker of the House of Representatives, mayHavePower, to cast tie‑breaking votes in some systems]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayHavePower
Context triple: [Speaker of the House of Representatives, mayHavePower, to cast tie‑breaking votes in some systems]
  • A. hasPower
    Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
  • B. typeOfPowerGranted chosen
    Indicates the specific kind or category of power or authority that is conferred from one entity to another.
  • C. hasPowerSource
    Indicates that an entity derives its operational energy or functionality from a specified power source.
  • D. grantedPower
    Indicates that one entity has conferred authority, control, or a specific capability to another entity.
  • E. mayHold
    Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
  • 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_69a498da82e08190ba833330d05f380f completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c6a44efc819084254614d8ea4669 completed March 1, 2026, 11:07 p.m.
PD Predicate disambiguation batch_69a4c486eacc81909c272f9bdf50a7c3 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:12 p.m.