Triple

T14853474
Position Surface form Disambiguated ID Type / Status
Subject Wardley E349289 entity
Predicate adjacentTo P224 FINISHED
Object Worsley E44025 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: Worsley | Statement: [Wardley, adjacentTo, Worsley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Worsley
Context triple: [Wardley, adjacentTo, Worsley]
  • A. Worsley chosen
    Worsley is a village in Greater Manchester, England, historically significant as a coal-mining and canal hub central to the early Industrial Revolution.
  • B. Levenshulme
    Levenshulme is a residential suburb in south Manchester, England, known for its diverse community and vibrant local markets.
  • C. Urmston
    Urmston is a suburban town in Greater Manchester, England, known primarily as a residential area within the Metropolitan Borough of Trafford.
  • D. Didsbury
    Didsbury is a suburban area of Manchester, England, known for its leafy residential streets, independent shops, and vibrant café and bar scene.
  • E. Droylsden
    Droylsden is a town in Greater Manchester, England, historically part of Lancashire and now a residential suburb of Manchester.
  • 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_69d822ed7e1881909b90fca143ad7e34 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded44318f0819080b6c599f2d3474f completed April 14, 2026, 11:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe6506ace48190819504b93f575660 completed May 8, 2026, 10:34 p.m.
Created at: April 10, 2026, 1:54 a.m.