Triple

T22112312
Position Surface form Disambiguated ID Type / Status
Subject Copeland E546447 entity
Predicate contains P35 FINISHED
Object Haverigg 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: Haverigg | Statement: [Copeland, contains, Haverigg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haverigg
Context triple: [Copeland, contains, Haverigg]
  • A. Haverigg chosen
    Haverigg is a coastal village in Cumbria, England, known for its sandy beach, dunes, and proximity to the Lake District.
  • B. Boarshead
    Boarshead is a small village in East Sussex, England, situated within the civil parish of Rotherfield.
  • C. Crofthaven
    Crofthaven is a terminus station on the fictional narrow-gauge Skarloey Railway in The Railway Series/Thomas & Friends universe.
  • D. Cogenhoe
    Cogenhoe is a village and civil parish in West Northamptonshire, England, known for its rural character and proximity to the historic Castle Ashby estate.
  • E. Perranzabuloe
    Perranzabuloe is a coastal parish in Cornwall, England, historically associated with Saint Piran and known for its early Christian heritage and extensive sand dunes.
  • 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1294ae7608190901745384a023bab completed April 28, 2026, 9:40 p.m.
Created at: April 16, 2026, 8:31 p.m.