Triple

T15248783
Position Surface form Disambiguated ID Type / Status
Subject Township Council–Manager E364458 entity
Predicate managerCoordinates P112058 FINISHED
Object delivery of township services 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: delivery of township services | Statement: [Township Council–Manager, managerCoordinates, delivery of township services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: managerCoordinates
Context triple: [Township Council–Manager, managerCoordinates, delivery of township services]
  • A. coordinateLocation
    Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
  • B. coordinatesPositionsIn
    Indicates that one entity organizes or aligns the positions or placement of other entities within a specified context or space.
  • C. headquartersCoordinates
    Indicates the geographic coordinates where an entity’s main headquarters is located.
  • D. coordinatesUseOf chosen
    Indicates that one entity organizes and manages the collaborative use or deployment of another entity’s resources, actions, or functions.
  • E. coordinateOn
    Indicates that two or more entities work together to organize, align, or manage a shared activity, process, or objective.
  • 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_69deca8d1bd48190a4b94f29b425e335 completed April 14, 2026, 11:15 p.m.
Created at: April 10, 2026, 3:13 a.m.