Triple

T6782519
Position Surface form Disambiguated ID Type / Status
Subject Audenshaw E155717 entity
Predicate adjacentTo P224 FINISHED
Object Droylsden E157234 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: Droylsden | Statement: [Audenshaw, adjacentTo, Droylsden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Droylsden
Context triple: [Audenshaw, adjacentTo, Droylsden]
  • A. Droylsden chosen
    Droylsden is a town in Greater Manchester, England, historically part of Lancashire and now a residential suburb of Manchester.
  • B. Levenshulme
    Levenshulme is a residential suburb in south Manchester, England, known for its diverse community and vibrant local markets.
  • C. Worsley
    Worsley is a village in Greater Manchester, England, historically significant as a coal-mining and canal hub central to the early Industrial Revolution.
  • 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. Prestwich
    Prestwich is a suburban town in Greater Manchester, England, known for its residential character and proximity to Manchester city centre.
  • 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_69c688162bf8819088b664b5c3b5be7a completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d289958481908ad4f9467a107083 completed March 27, 2026, 6:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69c712d5557881909614819deb335534 completed March 27, 2026, 11:29 p.m.
Created at: March 27, 2026, 2:14 p.m.