Triple

T34505370
Position Surface form Disambiguated ID Type / Status
Subject Bihar Lok Sabha constituencies E885868 entity
Predicate canHaveByElections P47256 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: [Bihar Lok Sabha constituencies, canHaveByElections, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canHaveByElections
Context triple: [Bihar Lok Sabha constituencies, canHaveByElections, yes]
  • A. hasByElections chosen
    Indicates that one entity conducts, experiences, or is associated with one or more by-elections in relation to another contextual entity (such as a jurisdiction, office, or time period).
  • B. canHoldSpecialElections
    Indicates that an entity has the authority or ability to conduct special elections outside the regular election schedule.
  • C. hasElectionsFor
    Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
  • D. hasElection
    Indicates that an entity conducts, holds, or is associated with an election event.
  • E. hasLocalGovernmentElections
    Indicates that local government bodies within a jurisdiction hold elections to choose their representatives or officials.
  • 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_69f349cc0220819081f154c6964f4dc2 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71fb1ab3881908e2f7c0e6f23db49 completed May 3, 2026, 10:13 a.m.
PD Predicate disambiguation batch_69f71cc6397881909aaad37a9daa8a7e completed May 3, 2026, 10 a.m.
Created at: May 1, 2026, 2:01 a.m.