Triple

T28812917
Position Surface form Disambiguated ID Type / Status
Subject Grundy County township system E727563 entity
Predicate usesElectedOffice P166504 FINISHED
Object township supervisor 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: township supervisor | Statement: [Grundy County township system, usesElectedOffice, township supervisor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesElectedOffice
Context triple: [Grundy County township system, usesElectedOffice, township supervisor]
  • A. usedByCandidateForOffice
    Indicates that something (such as a resource, tool, or material) is utilized by a person who is running for a specific public office in the context of their candidacy.
  • B. isElectoralOffice
    Indicates that the referenced position or role is an official public office filled through an electoral process.
  • C. electedOffice
    Indicates that an entity holds or has held a particular office or position as a result of an election.
  • D. isElectedFor
    Indicates that an entity attains a position, role, or office as the result of an election for that specific position.
  • E. nominatedForOffice
    Indicates that an entity has been formally put forward as a candidate to hold a particular office or position.
  • F. None of above. chosen

Provenance (4 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_69f0319c38948190bca746ad60fd25ba completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f6622808b48190bbabcc75288ab031 completed May 2, 2026, 8:44 p.m.
PD Predicate disambiguation batch_69f660f082508190a95a7888ad66cb2e completed May 2, 2026, 8:39 p.m.
PDg Predicate description generation batch_69f6617a7e7c81908cfac4a2250797ee completed May 2, 2026, 8:41 p.m.
Created at: April 28, 2026, 6:31 a.m.