Triple

T12077352
Position Surface form Disambiguated ID Type / Status
Subject Blaydon E287584 entity
Predicate hasBusServicesTo P3791 FINISHED
Object Consett E204561 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: Consett | Statement: [Blaydon, hasBusServicesTo, Consett]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Consett
Context triple: [Blaydon, hasBusServicesTo, Consett]
  • A. Consett chosen
    Consett is a town in north-west County Durham, England, historically known for its steelworks and industrial heritage.
  • B. Peterlee
    Peterlee is a post-war new town in North East England, established to serve nearby coal mining communities.
  • C. Skelmersdale
    Skelmersdale is a planned new town in West Lancashire, England, known for its extensive roundabout road system and post-war housing developments.
  • D. Spennymoor
    Spennymoor is a small town in County Durham, England, known historically for its coal mining heritage and later as a residential and commuter community near Durham and Bishop Auckland.
  • E. Ormskirk
    Ormskirk is a historic market town in West Lancashire, England, known for its traditional market, distinctive parish church, and proximity to both Liverpool and the surrounding countryside.
  • 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_69d6ab4846e081908ee7bbd66a6d3459 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9045ceeec81909427cae8972eed26 completed April 10, 2026, 2:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f660f48881908d50bf27b0892953 completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:48 p.m.