Triple

T20993275
Position Surface form Disambiguated ID Type / Status
Subject Western Fells E517077 entity
Predicate hasNotableSummit P8666 FINISHED
Object High Crag 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: High Crag | Statement: [Western Fells, hasNotableSummit, High Crag]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: High Crag
Context triple: [Western Fells, hasNotableSummit, High Crag]
  • A. High Crag chosen
    High Crag is a prominent fell in England’s Lake District, forming part of the dramatic ridge above Buttermere and Ennerdale.
  • B. Ill Crag
    Ill Crag is a prominent high fell in England’s Lake District, forming part of the Scafell massif and offering rugged terrain and expansive mountain views.
  • C. Great Crag
    Great Crag is a small but prominent fell in England’s Lake District, known for its rugged terrain and scenic views over the surrounding Central Fells.
  • D. Loft Crag
    Loft Crag is a prominent rocky fell in England’s Lake District, popular with walkers for its craggy summit and views over Great Langdale.
  • E. Stirrup Crag
    Stirrup Crag is a rocky subsidiary top on the Yewbarrow ridge in the Lake District, known for its steep, rugged terrain and scrambling routes.
  • 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_69e0b5006e2881909fc2383f841740cc completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc1d829081908de889c542734393 completed April 21, 2026, 4:25 a.m.
Created at: April 16, 2026, 1:50 p.m.