Triple

T16897237
Position Surface form Disambiguated ID Type / Status
Subject Dovedale E424337 entity
Predicate hasLandmark P105 FINISHED
Object Thorpe Cloud E453385 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: Thorpe Cloud | Statement: [Dovedale, hasLandmark, Thorpe Cloud]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thorpe Cloud
Context triple: [Dovedale, hasLandmark, Thorpe Cloud]
  • A. Thorpe Cloud chosen
    Thorpe Cloud is a prominent limestone hill in the Peak District of England, known for its distinctive conical shape and panoramic views over Dovedale.
  • B. Thorpe
    Thorpe is a village in the English county of Surrey, located within the TW (Twickenham) postcode area.
  • C. Thorpe
    Thorpe is an English surname most notably associated with Jeremy Thorpe, a prominent 20th-century British politician and former leader of the Liberal Party.
  • D. Thorpe
    Thorpe is a small village and civil parish located within the rural district of Howdenshire in the East Riding of Yorkshire, England.
  • E. Thorpe, Derbyshire
    Thorpe, Derbyshire is a small village in the Peak District of England, known as a popular base for walkers exploring the scenic Dovedale valley and surrounding countryside.
  • 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_69d889da3e8c8190a2b118f383f0beac completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3c8d880208190ad2b2c8616b54ea3 completed April 18, 2026, 6:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c7ad473081908b1c1d9524cf64a6 completed May 10, 2026, 6 p.m.
Created at: April 10, 2026, 5:29 a.m.