Triple

T4652424
Position Surface form Disambiguated ID Type / Status
Subject Stoke-on-Trent E102325 entity
Predicate formedFrom P402 FINISHED
Object Longton E385256 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: Longton | Statement: [Stoke-on-Trent, formedFrom, Longton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Longton
Context triple: [Stoke-on-Trent, formedFrom, Longton]
  • A. Longton chosen
    Longton is a town in Stoke-on-Trent, Staffordshire, England, historically known as one of the six pottery towns of the region.
  • B. Etwall
    Etwall is a village and civil parish in the county of Derbyshire, England, known for its historic buildings and annual well dressing festival.
  • C. 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.
  • D. Northenden
    Northenden is a suburban area of Manchester, England, situated on the River Mersey in the south of the city.
  • E. Nechells
    Nechells is an inner-city district of Birmingham, England, known for its industrial heritage and residential neighborhoods.
  • 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_69bd43d71a308190afea7280841b0de8 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd6314883481908f085a7af497b0d8 completed March 20, 2026, 3:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69be0374967c8190b77bcd3ea1c4d59d completed March 21, 2026, 2:33 a.m.
Created at: March 20, 2026, 1:14 p.m.