Triple

T22725351
Position Surface form Disambiguated ID Type / Status
Subject Kimberley, Nottinghamshire E561976 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Greasley NE NERFINISHED

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: Greasley | Statement: [Kimberley, Nottinghamshire, hasNearbySettlement, Greasley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Greasley
Context triple: [Kimberley, Nottinghamshire, hasNearbySettlement, Greasley]
  • A. Greasley chosen
    Greasley is a village and civil parish in the Broxtowe district of Nottinghamshire, England.
  • B. Shiregreen
    Shiregreen is a residential suburb in the northern part of Sheffield, England, characterized by large housing estates and local community amenities.
  • C. Gossops Green
    Gossops Green is a residential neighbourhood and suburb within the town of Crawley in West Sussex, England.
  • D. Skelton Green
    Skelton Green is a small village in North Yorkshire, England, situated near the North Sea coast and historically associated with the Teesside area.
  • E. Kearsley
    Kearsley is a small town in the Hunter Region of New South Wales, Australia, known historically for its coal mining and rural community character.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2454fc984819088213b58ee87a002 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17929710c81909a895622ee32920e completed April 29, 2026, 3:21 a.m.
Created at: April 17, 2026, 3:20 p.m.