Triple

T15248751
Position Surface form Disambiguated ID Type / Status
Subject Township Council–Manager E364458 entity
Predicate managerReportsTo P5751 FINISHED
Object township council 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 council | Statement: [Township Council–Manager, managerReportsTo, township council]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: managerReportsTo
Context triple: [Township Council–Manager, managerReportsTo, township council]
  • A. officeHolderReportsTo
    Indicates that one office holder is subordinate to and formally reports to another office holder within an organizational or governmental hierarchy.
  • B. designatesReportingLineTo
    Indicates that one entity is formally assigned as the reporting line or supervisory authority for another entity.
  • C. officeHierarchy chosen
    Indicates a reporting or supervisory relationship between positions within an office, defining who is above or below whom in the organizational chain of command.
  • D. leadershipRolesOverseenBy
    Indicates that certain leadership roles are supervised, managed, or overseen by a specified entity.
  • E. reportsSymbolicallyTo
    Indicates that one entity formally reports to another through symbolic, representational, or non-literal means rather than through direct, operational authority.
  • 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_69d85a0dde7481908fc64d1e82d5d20d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e007f62b9c8190b9ad40e2d1912b63 completed April 15, 2026, 9:49 p.m.
PD Predicate disambiguation batch_69deca899d5c8190be4a7c71e1683c69 completed April 14, 2026, 11:15 p.m.
Created at: April 10, 2026, 3:13 a.m.