Triple

T9140631
Position Surface form Disambiguated ID Type / Status
Subject Teesside urban area E219315 entity
Predicate hasTown P847 FINISHED
Object Thornaby E783771 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: Thornaby | Statement: [Teesside urban area, hasTown, Thornaby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thornaby
Context triple: [Teesside urban area, hasTown, Thornaby]
  • A. Thornaby-on-Tees chosen
    Thornaby-on-Tees is a town in North Yorkshire, England, situated on the River Tees and forming part of the wider Teesside conurbation.
  • B. Milnrow
    Milnrow is a town in Greater Manchester, England, historically part of Lancashire and known for its textile heritage and proximity to the Pennine hills.
  • C. Wansbeck
    Wansbeck is a UK parliamentary constituency in Northumberland that includes the town of Ashington and surrounding communities in northeast England.
  • D. Brighouse
    Brighouse is a market and industrial town in the metropolitan borough of Calderdale in northern England.
  • E. Northenden
    Northenden is a suburban area of Manchester, England, situated on the River Mersey in the south of the city.
  • 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_69ca83e012288190a5771058adbaabd2 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8f2537881908956a9b0516e2d49 completed April 1, 2026, 5:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d065c6fcc081908298dd12477c2345 completed April 4, 2026, 1:13 a.m.
Created at: March 30, 2026, 7:19 p.m.