Triple

T24814387
Position Surface form Disambiguated ID Type / Status
Subject Great Sca Fell E620873 entity
Predicate hasTypicalAscentFrom P37604 FINISHED
Object Caldbeck area LITERAL 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: Caldbeck area | Statement: [Great Sca Fell, hasTypicalAscentFrom, Caldbeck area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypicalAscentFrom
Context triple: [Great Sca Fell, hasTypicalAscentFrom, Caldbeck area]
  • A. typicalAscentStartPoint chosen
    Indicates the usual or most common location from which an ascent or climb is begun.
  • B. typicalAscentCombinedWith
    Indicates that one ascent or climbing route is normally undertaken together with another as part of a standard or customary combined itinerary.
  • C. hasPopularAscentRouteFrom
    Indicates that there exists a commonly used or well-known route for ascending to a place or peak starting from the specified origin location.
  • D. hasClimbFrom
    Indicates a relationship where one location or object serves as the starting point from which a climb or ascent to another location or object begins.
  • E. hasFirstRecordedAscent
    Indicates that a particular ascent is the earliest known or documented successful climb of a specific route, peak, or climbing objective.
  • F. None of above.

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_69e2fabfd4648190bd0e5c7f4dbb6cab completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f6135293908190809e255bf6334760 completed May 2, 2026, 3:08 p.m.
PD Predicate disambiguation batch_69f611a72780819082f44e66ca2c6ac9 completed May 2, 2026, 3 p.m.
Created at: April 18, 2026, 5 a.m.