Triple

T23041314
Position Surface form Disambiguated ID Type / Status
Subject Hellingly E573743 entity
Predicate governingBody P46 FINISHED
Object Hellingly Parish Council — NE NERFINISHED

How this triple was built (3 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: Hellingly Parish Council | Statement: [Hellingly, governingBody, Hellingly Parish Council]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Hellingly Parish Council
Context triple: [Hellingly, governingBody, Hellingly Parish Council]
  • A. Haughley Parish Council
    Haughley Parish Council is the local elected authority responsible for representing residents and managing community affairs and services in the village of Haughley, Suffolk, England.
  • B. Ryhall Parish Council
    Ryhall Parish Council is the local elected authority responsible for representing residents and managing community affairs and services within the village and parish of Ryhall in Rutland, England.
  • C. Gillingham Parish Council
    Gillingham Parish Council is the local elected authority responsible for representing and managing community affairs in the village of Gillingham in Suffolk, England.
  • D. Hildenborough Parish Council
    Hildenborough Parish Council is the local elected authority responsible for representing residents and managing community affairs in the village of Hildenborough, Kent, England.
  • E. Sweffling Parish Council
    Sweffling Parish Council is the local elected authority responsible for representing residents and managing community affairs in the village of Sweffling, Suffolk, England.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Hellingly Parish Council
Target entity description: Hellingly Parish Council is the local elected authority responsible for representing and managing community affairs and services in the village and civil parish of Hellingly, East Sussex, England.
  • A. Haughley Parish Council
    Haughley Parish Council is the local elected authority responsible for representing residents and managing community affairs and services in the village of Haughley, Suffolk, England.
  • B. Ryhall Parish Council
    Ryhall Parish Council is the local elected authority responsible for representing residents and managing community affairs and services within the village and parish of Ryhall in Rutland, England.
  • C. Gillingham Parish Council
    Gillingham Parish Council is the local elected authority responsible for representing and managing community affairs in the village of Gillingham in Suffolk, England.
  • D. Hildenborough Parish Council
    Hildenborough Parish Council is the local elected authority responsible for representing residents and managing community affairs in the village of Hildenborough, Kent, England.
  • E. Sweffling Parish Council
    Sweffling Parish Council is the local elected authority responsible for representing residents and managing community affairs in the village of Sweffling, Suffolk, England.
  • F. None of above. chosen

Provenance (2 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_69e245b9c11481909d06c872214d21af completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18513fc54819096d761a0be75b774 completed April 29, 2026, 4:12 a.m.
Created at: April 17, 2026, 3:53 p.m.