Triple

T27106372
Position Surface form Disambiguated ID Type / Status
Subject Craggy Pinnacle Trail E686589 entity
Predicate hasTrailheadNearMilepost P11755 FINISHED
Object Blue Ridge Parkway milepost 364 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: Blue Ridge Parkway milepost 364 | Statement: [Craggy Pinnacle Trail, hasTrailheadNearMilepost, Blue Ridge Parkway milepost 364]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrailheadNearMilepost
Context triple: [Craggy Pinnacle Trail, hasTrailheadNearMilepost, Blue Ridge Parkway milepost 364]
  • A. hasTrailheadAt
    Indicates that a trail or route begins or has its official starting point at a specified location.
  • B. hasNearbyTrailheadFor chosen
    Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
  • C. hasTrailheadSignage
    Indicates that a trailhead is equipped with signage providing information or guidance to users.
  • D. hasTrailheadBelow
    Indicates that the starting point of a trail is located at a lower elevation or position relative to another referenced feature or location.
  • E. trailMilepostOn
    Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
  • 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_69ef148accd48190b6ed6e13a15f2a4f completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69fba78aca4c8190b8f1831e8cc04e06 completed May 6, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69fba34a65a4819088bac6c17542d71c completed May 6, 2026, 8:23 p.m.
Created at: April 27, 2026, 8:51 a.m.