Triple

T23498339
Position Surface form Disambiguated ID Type / Status
Subject Colwick E571764 entity
Predicate hasElectoralWard P962 FINISHED
Object Colwick ward 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: Colwick ward | Statement: [Colwick, hasElectoralWard, Colwick ward]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Colwick ward
Context triple: [Colwick, hasElectoralWard, Colwick ward]
  • A. Colwick chosen
    Colwick is a village and civil parish in Nottinghamshire, England, situated just east of Nottingham along the River Trent.
  • B. Ardwick
    Ardwick is a district of Manchester, England, known historically as an industrial and residential area that once lent its name to the football club now known as Manchester City.
  • C. Fulwell ward
    Fulwell ward is a local electoral division in the London Borough of Richmond upon Thames, represented on the borough council.
  • D. Werneth ward
    Werneth ward is an electoral division within the Metropolitan Borough of Oldham in Greater Manchester, England.
  • E. Elswick ward
    Elswick ward is an electoral division within the city of Newcastle upon Tyne, England, used for local government representation and administration.
  • 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_69e245b4829881909b77a70e942bbd54 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a7e184ec8190aff3677c9b00a8f2 completed April 29, 2026, 6:40 a.m.
Created at: April 17, 2026, 6:06 p.m.