Triple

T16093661
Position Surface form Disambiguated ID Type / Status
Subject Select Board and Town Meeting E390424 entity
Predicate electiveOfficesInvolved P6491 FINISHED
Object select board members 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: select board members | Statement: [Select Board and Town Meeting, electiveOfficesInvolved, select board members]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: electiveOfficesInvolved
Context triple: [Select Board and Town Meeting, electiveOfficesInvolved, select board members]
  • A. electedOffice
    Indicates that an entity holds or has held a particular office or position as a result of an election.
  • B. isElectoralOffice chosen
    Indicates that the referenced position or role is an official public office filled through an electoral process.
  • C. possibleOfficeHeld
    Indicates that an entity may have held, or is a candidate to have held, a particular office or position, without asserting it as a confirmed fact.
  • D. involvesOfficeHolder
    Indicates that the relationship or action includes or pertains to a person currently holding a specific office or official position.
  • E. alsoHoldsOfficeOf
    Indicates that an entity currently holding one office or position simultaneously holds another office or position as well.
  • 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_69d87f198bc48190a8b7e53ca15b7ead completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e1ff63edb0819092cbb671967bbdcd completed April 17, 2026, 9:37 a.m.
PD Predicate disambiguation batch_69e182804208819087f35307cd6e4103 completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 4:59 a.m.