Triple

T16635670
Position Surface form Disambiguated ID Type / Status
Subject London Road, Peterborough E404192 entity
Predicate hasNearbyNeighbourhood P4647 FINISHED
Object Stanground E206525 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: Stanground | Statement: [London Road, Peterborough, hasNearbyNeighbourhood, Stanground]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stanground
Context triple: [London Road, Peterborough, hasNearbyNeighbourhood, Stanground]
  • A. Stanground chosen
    Stanground is a residential suburb and former village located within the city of Peterborough in Cambridgeshire, England.
  • B. Grindon
    Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
  • C. Nettlestone
    Nettlestone is a village on the Isle of Wight in England, situated close to the coastal area around Seaview.
  • D. Stotfield
    Stotfield is a coastal residential area forming part of the town of Lossiemouth in Moray, Scotland.
  • E. Sherkston
    Sherkston is a lakeside community in Ontario, Canada, known for its beaches, campgrounds, and recreational resort atmosphere along Lake Erie.
  • 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_69d8838a41f08190b0c3f79c47df5078 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e378e999d48190bff680040dbc883d completed April 18, 2026, 12:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084b984d081909f76ef874431ff40 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:17 a.m.