Triple
T24396076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berney Arms railway station |
E615029
|
entity |
| Predicate | distanceToNearestRoadAccess |
P32541
|
FINISHED |
| Object | several miles on footpaths |
—
|
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: several miles on footpaths | Statement: [Berney Arms railway station, distanceToNearestRoadAccess, several miles on footpaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNearestRoadAccess Context triple: [Berney Arms railway station, distanceToNearestRoadAccess, several miles on footpaths]
-
A.
distanceFromRoads
Indicates the measured or estimated spatial distance between a location and the nearest road.
-
B.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
-
C.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
-
D.
hasRoadProximity
Indicates that one entity is located near or adjacent to a road in terms of spatial proximity.
-
E.
trekDistanceFromRoadHead
chosen
Indicates the distance one must trek from the road head (road access point) to reach a specified location.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294d69b5c81908cf6143374934f5c |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.