Triple

T22593077
Position Surface form Disambiguated ID Type / Status
Subject Leicestershire County Council E564999 entity
Predicate seat P75 FINISHED
Object Glenfield NE NERFINISHED

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: Glenfield | Statement: [Leicestershire County Council, seat, Glenfield]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Glenfield
Context triple: [Leicestershire County Council, seat, Glenfield]
  • A. Glenfield
    Glenfield is a residential suburb in Sydney, New South Wales, known for its transport links and proximity to Campbelltown and other south-western Sydney suburbs.
  • B. Glenfield
    Glenfield is a residential suburb on Auckland's North Shore in New Zealand, known for its shopping mall and family-oriented community.
  • C. Glenfield chosen
    Glenfield is a village and civil parish in Leicestershire, England, situated just northwest of Leicester.
  • D. Blanefield
    Blanefield is a small village in central Scotland, situated near the Campsie Fells and known for its scenic rural setting within the Stirling area.
  • E. Wynnefield
    Wynnefield is a residential neighborhood in West Philadelphia known for its tree-lined streets, diverse community, and proximity to Saint Joseph’s University.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e245836014819091b91ed3074742a3 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f16163cb248190b377b110d80a6730 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 2:49 p.m.