Triple

T16772350
Position Surface form Disambiguated ID Type / Status
Subject Bradford, Manchester E407628 entity
Predicate locatedNear P294 FINISHED
Object Beswick E99814 NE 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: Beswick | Statement: [Bradford, Manchester, locatedNear, Beswick]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beswick
Context triple: [Bradford, Manchester, locatedNear, Beswick]
  • A. Beswick
    Beswick is a remote Aboriginal community in Australia's Northern Territory that serves as a central hub for the Jawoyn people.
  • B. Beswick chosen
    Beswick is an inner-city district of Manchester, England, known for its industrial heritage and ongoing urban regeneration.
  • C. Blisworth
    Blisworth is a village in Northamptonshire, England, known for its historic location on the Grand Union Canal near the Blisworth Tunnel.
  • D. Banwell
    Banwell is a village and civil parish in North Somerset, England, known for its historic caves and medieval architecture.
  • E. Bywell
    Bywell is a small historic village in Northumberland, England, situated on the north bank of the River Tyne and known for its medieval churches and castle ruins.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8839174188190909f190097207065 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b036ff788190bd9f166c3f127818 completed April 18, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a5361c3881909be0fb9b83a59993 completed May 10, 2026, 3:33 p.m.
Created at: April 10, 2026, 5:21 a.m.