Triple
T25168850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brim Fell |
E630258
|
entity |
| Predicate | ridgeRoute |
P111066
|
FINISHED |
| Object | Coniston Old Man–Brim Fell–Swirl How ridge |
—
|
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: Coniston Old Man–Brim Fell–Swirl How ridge | Statement: [Brim Fell, ridgeRoute, Coniston Old Man–Brim Fell–Swirl How ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ridgeRoute Context triple: [Brim Fell, ridgeRoute, Coniston Old Man–Brim Fell–Swirl How ridge]
-
A.
rangeRoad
Indicates that a road or route extends across or through a specified geographic range or area.
-
B.
ridgeway
Indicates a relationship where something is associated with, located on, or follows along a ridgeway (a path or route along a ridge).
-
C.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
D.
hasRidgeRoute
chosen
Indicates that one entity possesses or is associated with a route that follows or traverses a ridge.
-
E.
isMountainRoad
Indicates that a given road is classified as a mountain road, typically traversing or situated within mountainous terrain.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d44f48c8190943b3b22651be3c4 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:19 p.m.