Triple

T14680481
Position Surface form Disambiguated ID Type / Status
Subject West Harptree E344766 entity
Predicate hasNearbyVillage P4647 FINISHED
Object Ubley E188971 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: Ubley | Statement: [West Harptree, hasNearbyVillage, Ubley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ubley
Context triple: [West Harptree, hasNearbyVillage, Ubley]
  • A. Ubley chosen
    Ubley is a small rural village in Somerset, England, situated near the northern edge of the Mendip Hills.
  • B. Banwell
    Banwell is a village and civil parish in North Somerset, England, known for its historic caves and medieval architecture.
  • C. Ruxley
    Ruxley is a locality in the London Borough of Bromley, England, known for its mix of suburban development and nearby nature reserves such as the Ruxley Gravel Pits.
  • D. Upleatham
    Upleatham is a small village in North Yorkshire, England, known for its rural character and historic parish church.
  • E. Blackley
    Blackley is a suburban area of Manchester, England, known for its residential neighborhoods and proximity to the River Irk and local green spaces.
  • 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_69d822e34b348190ada4d1cdb6c7c226 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb5692284819090f775be8e478522 completed April 14, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fde180ff0c8190a8b7c7804e36c3f8 completed May 8, 2026, 1:13 p.m.
Created at: April 10, 2026, 1:28 a.m.