Triple

T28812916
Position Surface form Disambiguated ID Type / Status
Subject Grundy County township system E727563 entity
Predicate usesGovernmentBodyType P130835 FINISHED
Object township board 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 board | Statement: [Grundy County township system, usesGovernmentBodyType, township board]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesGovernmentBodyType
Context triple: [Grundy County township system, usesGovernmentBodyType, township board]
  • A. hasGovernmentalBodyType chosen
    Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
  • B. basedInGovernmentType
    Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
  • C. governmentBodyUser
    Indicates a relationship where a user is associated with, represents, or acts on behalf of a specific government body.
  • D. usesGovernmentBuilding
    Indicates that an entity makes use of a government-owned or government-operated building for some purpose or activity.
  • E. usedInGovernmentBody
    Indicates that an entity is employed by, serves within, or is otherwise functionally involved in the operations of a government body.
  • 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_69f0319c38948190bca746ad60fd25ba completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f658f05db88190b613173eece383d4 completed May 2, 2026, 8:05 p.m.
PD Predicate disambiguation batch_69f65760fd3081908ffe014a5e2bf069 completed May 2, 2026, 7:58 p.m.
Created at: April 28, 2026, 6:31 a.m.