Triple

T19007762
Position Surface form Disambiguated ID Type / Status
Subject Warsop E465133 entity
Predicate hasPart P35 FINISHED
Object Church Warsop 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: Church Warsop | Statement: [Warsop, hasPart, Church Warsop]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Church Warsop
Context triple: [Warsop, hasPart, Church Warsop]
  • A. Warsop chosen
    Warsop is a small town and civil parish in Nottinghamshire, England, historically linked to coal mining and situated near the larger market town of Mansfield.
  • B. Great Wakering
    Great Wakering is a village and civil parish in Essex, England, situated near the North Sea coast east of Southend-on-Sea.
  • C. Hawkenbury
    Hawkenbury is a residential suburb and community area of Royal Tunbridge Wells in Kent, England.
  • D. Swerford
    Swerford is a small rural village in Oxfordshire, England, known for its historic stone cottages and picturesque countryside setting.
  • E. Hartsop
    Hartsop is a small, traditional Lakeland village in the English Lake District, known for its stone cottages and scenic valley setting near Ullswater.
  • 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_69d8dd01a56c81909694a128c66b21d7 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6a623c481908d22c9bfad9e2939 completed April 20, 2026, 7:32 a.m.
Created at: April 10, 2026, 12:01 p.m.