Triple

T22592993
Position Surface form Disambiguated ID Type / Status
Subject Charnwood E564997 entity
Predicate contains P35 FINISHED
Object Queniborough 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: Queniborough | Statement: [Charnwood, contains, Queniborough]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Queniborough
Context triple: [Charnwood, contains, Queniborough]
  • A. Queniborough chosen
    Queniborough is a village and civil parish in Leicestershire, England, known for its historic thatched cottages and rural character.
  • B. Aldborough
    Aldborough was a former parliamentary borough in England that historically returned members to the British House of Commons.
  • C. Aldbrough
    Aldbrough is a coastal village in the East Riding of Yorkshire, England, known for its rural setting and proximity to the North Sea.
  • D. Buntingford
    Buntingford is a small historic market town in Hertfordshire, England, known for its traditional high street and rural surroundings.
  • E. Brundall
    Brundall is a village in Norfolk, England, known for its riverside location in the Norfolk Broads and its boating and leisure activities.
  • 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.