Triple

T23876047
Position Surface form Disambiguated ID Type / Status
Subject Icknield Way Trail E592867 entity
Predicate usesWaymarks P47567 FINISHED
Object Icknield Way Trail waymarks 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: Icknield Way Trail waymarks | Statement: [Icknield Way Trail, usesWaymarks, Icknield Way Trail waymarks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesWaymarks
Context triple: [Icknield Way Trail, usesWaymarks, Icknield Way Trail waymarks]
  • A. hasWaypoint
    Indicates that an entity follows a path or route that includes a specific intermediate location (waypoint) along its trajectory.
  • B. trailsMarkedBy chosen
    Indicates that a trail or path is designated or identified by specific markers, signs, or blazes placed along its route.
  • C. waymarkingStatus
    Indicates the current state or condition of a waymarking process, such as whether a location or route has been identified, recorded, approved, or otherwise classified in a waymarking system.
  • D. hasTrailheads
    Indicates that one location or area contains or provides access points where trails begin.
  • E. usedToNavigate
    Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
  • 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_69e25d23a5c88190ae3999c70ca15e08 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1cc012974819090b34aad6a230f81 completed April 29, 2026, 9:14 a.m.
PD Predicate disambiguation batch_69f1614a65a88190bde1efb368a151e4 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:15 p.m.