Triple

T6144268
Position Surface form Disambiguated ID Type / Status
Subject Carlton E137035 entity
Predicate hasNeighbouringSettlement P4647 FINISHED
Object Mapperley E556477 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: Mapperley | Statement: [Carlton, hasNeighbouringSettlement, Mapperley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mapperley
Context triple: [Carlton, hasNeighbouringSettlement, Mapperley]
  • A. Mapperley chosen
    Mapperley is a suburban residential area in the Nottingham region of England, known for its local amenities and proximity to Arnold.
  • B. Gamesley
    Gamesley is a residential area and former council estate on the outskirts of Glossop in Derbyshire, England.
  • C. Mobberley
    Mobberley is a rural village and civil parish in Cheshire, England, known for its historic church, traditional pubs, and proximity to Manchester Airport.
  • D. Popley
    Popley is a residential suburb and housing estate in the northern part of Basingstoke, Hampshire, England.
  • E. Homersfield
    Homersfield is a small village and civil parish on the River Waveney in eastern England, known for its historic bridge and rural Suffolk setting.
  • 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_69c008a2c6308190a56519b22d55d083 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05cb645508190aea2d77c9de174ba completed March 22, 2026, 9:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c135f88db881908b8a5d9c35bf0fbb completed March 23, 2026, 12:45 p.m.
Created at: March 22, 2026, 4:16 p.m.