Triple

T8031478
Position Surface form Disambiguated ID Type / Status
Subject South Manchester E186990 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Levenshulme E410701 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: Levenshulme | Statement: [South Manchester, hasNeighbourhood, Levenshulme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Levenshulme
Context triple: [South Manchester, hasNeighbourhood, Levenshulme]
  • A. Levenshulme chosen
    Levenshulme is a residential suburb in south Manchester, England, known for its diverse community and vibrant local markets.
  • B. Worsley
    Worsley is a village in Greater Manchester, England, historically significant as a coal-mining and canal hub central to the early Industrial Revolution.
  • C. Urmston
    Urmston is a suburban town in Greater Manchester, England, known primarily as a residential area within the Metropolitan Borough of Trafford.
  • D. Droylsden
    Droylsden is a town in Greater Manchester, England, historically part of Lancashire and now a residential suburb of Manchester.
  • E. Moss Side
    Moss Side is an inner-city district of Manchester, England, known for its diverse community, rich cultural history, and significant role in the city’s social and musical life.
  • 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_69ca82ae2d1081909dbfee42b41db419 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3eef921081908d0ea21f142c175a completed March 31, 2026, 3:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd6759e83c8190869732f955279cee completed April 1, 2026, 6:43 p.m.
Created at: March 30, 2026, 5:22 p.m.