Triple

T21491125
Position Surface form Disambiguated ID Type / Status
Subject Rolvenden E530237 entity
Predicate civilParish P2739 FINISHED
Object Rolvenden 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: Rolvenden | Statement: [Rolvenden, civilParish, Rolvenden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rolvenden
Context triple: [Rolvenden, civilParish, Rolvenden]
  • A. Rolvenden chosen
    Rolvenden is a rural village and civil parish in the Ashford district of Kent, England, known for its traditional English countryside character and historic buildings.
  • B. Rippingale
    Rippingale is a rural village and civil parish in the South Kesteven district of Lincolnshire, England.
  • C. Riggindale
    Riggindale is a remote, narrow valley in the Lake District of Cumbria, England, known for its rugged scenery and proximity to the High Street ridge.
  • D. Grindale
    Grindale is a small village in the East Riding of Yorkshire, England, situated within the historic wapentake of Dickering.
  • E. Turvey
    Turvey is a historic village and civil parish in Bedfordshire, England, known for its riverside setting on the River Great Ouse and notable stone bridges and buildings.
  • 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_69e0c45bd15481909fba5910765cdda2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea3aee648190ba845f0c7d8110dd completed April 23, 2026, 9:45 a.m.
Created at: April 16, 2026, 6:22 p.m.