Triple

T1092161
Position Surface form Disambiguated ID Type / Status
Subject North Bridge E24188 entity
Predicate hasWalkingTrailConnection P14127 FINISHED
Object Battle Road and related park trails 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: Battle Road and related park trails | Statement: [North Bridge, hasWalkingTrailConnection, Battle Road and related park trails]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWalkingTrailConnection
Context triple: [North Bridge, hasWalkingTrailConnection, Battle Road and related park trails]
  • A. TrailLinkIs chosen
    Indicates that one trail segment is connected to or continues from another trail segment.
  • B. hasNearbyTrailheadFor
    Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
  • C. hasHikingTrailToTop
    Indicates that there exists a hiking trail leading from a starting location to the top or summit of a specified destination.
  • D. hasNearbyTrail
    Indicates that one entity is located close to or within a short distance of a trail.
  • E. hasRailTrail
    Indicates that one location or entity possesses, includes, or is connected by a rail trail (a recreational trail converted from or running along a former or existing railway corridor) to another location or entity.
  • 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_69a49404428c819092dcc9632f5f7b8b completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b982018481908b222df095e318c0 completed March 1, 2026, 10:11 p.m.
PD Predicate disambiguation batch_69a4b741b0cc8190be001a16a81f6d9e completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.