Triple

T7403346
Position Surface form Disambiguated ID Type / Status
Subject Eccles Line E170803 entity
Predicate servesCommunity P82 FINISHED
Object Langworthy E161820 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: Langworthy | Statement: [Eccles Line, servesCommunity, Langworthy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Langworthy
Context triple: [Eccles Line, servesCommunity, Langworthy]
  • A. Langworthy chosen
    Langworthy is a residential district in Salford, Greater Manchester, known for its urban regeneration and proximity to Manchester city centre.
  • B. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • C. Walton-on-the-Hill
    Walton-on-the-Hill is a village in Surrey, England, known for its picturesque setting on the North Downs and proximity to Epsom Downs and major golf courses.
  • D. Horbury
    Horbury is a town in West Yorkshire, England, historically part of the Wakefield area and known for its industrial heritage and parish church.
  • E. Wraysbury
    Wraysbury is a village and civil parish in Berkshire, England, situated near the River Thames and known for its historic sites and proximity to Windsor.
  • 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_69c68a6010108190925e5284de022660 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f26ea27c8190a55e0e0314b463d8 completed March 27, 2026, 9:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c81110d7648190a8938db7061be454 completed March 28, 2026, 5:34 p.m.
Created at: March 27, 2026, 3:10 p.m.