Triple

T8194803
Position Surface form Disambiguated ID Type / Status
Subject Bedford Central School District E191401 entity
Predicate hasSchoolBoardElections P49163 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: [Bedford Central School District, hasSchoolBoardElections, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSchoolBoardElections
Context triple: [Bedford Central School District, hasSchoolBoardElections, yes]
  • A. hasSchoolBoardElectionLevel
    Indicates the governmental or administrative level (e.g., local, regional, state) at which a school board election is held or governed.
  • B. schoolBoardElected
    Indicates that a school board has been chosen or selected through an election process.
  • 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 chosen
    Indicates that an entity conducts, holds, or is associated with an election event.
  • E. hasByElections
    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).
  • 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_69ca82c6e9548190a4c5ca14516e4417 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb5c20fbd08190b9966e3c967e9c71 completed March 31, 2026, 5:31 a.m.
PD Predicate disambiguation batch_69cb36aac86081909b83636e352e0ced completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:42 p.m.