Triple
T27389226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathblane |
E691472
|
entity |
| Predicate | hasWalkingRoutePassingNearby |
P76707
|
FINISHED |
| Object | West Highland Way |
—
|
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: West Highland Way | Statement: [Strathblane, hasWalkingRoutePassingNearby, West Highland Way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkingRoutePassingNearby Context triple: [Strathblane, hasWalkingRoutePassingNearby, West Highland Way]
-
A.
hasNearbyWalkingRoutes
chosen
Indicates that there are walkable paths or routes located close to the referenced entity.
-
B.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
C.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
D.
hasWalkingRouteConnection
Indicates that there is a walkable path or route directly connecting two locations.
-
E.
hasWalkingAllowed
Indicates that walking is permitted within or across the referenced area or context.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 12:25 p.m.