Triple

T20344324
Position Surface form Disambiguated ID Type / Status
Subject Bingley E495824 entity
Predicate hasNeighbour P5707 FINISHED
Object Eldwick 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: Eldwick | Statement: [Bingley, hasNeighbour, Eldwick]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eldwick
Context triple: [Bingley, hasNeighbour, Eldwick]
  • A. Eldwick chosen
    Eldwick is a village in West Yorkshire, England, situated near Bingley on the edge of the Yorkshire Dales.
  • B. Windlestone
    Windlestone is a village in County Durham, England, known for its historic country house, Windlestone Hall, and its rural surroundings.
  • C. Elswick
    Elswick is a district in Newcastle upon Tyne, England, historically known as a major industrial and shipbuilding center.
  • D. Elswick
    Elswick is a small rural village and civil parish in Lancashire, England, known for its countryside setting within the Borough of Fylde.
  • E. Stonethwaite
    Stonethwaite is a small rural village in the Borrowdale valley of England’s Lake District, known for its scenic landscapes and traditional stone-built houses.
  • 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_69e0b4a3320881909495ae8bc30bc2dc completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67837bef8819091e552d1c8a1665c completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:24 a.m.