Triple
T25023146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lonscale Fell |
E626632
|
entity |
| Predicate | hasRouteVia |
P4374
|
FINISHED |
| Object | Glenderaterra Valley |
—
|
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: Glenderaterra Valley | Statement: [Lonscale Fell, hasRouteVia, Glenderaterra Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteVia Context triple: [Lonscale Fell, hasRouteVia, Glenderaterra Valley]
-
A.
hasRoute
chosen
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
C.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
D.
hasRouteNetwork
Indicates that one entity possesses, is associated with, or is covered by a specific route network connecting multiple locations or paths.
-
E.
hasRouteConsideration
Indicates that one entity takes another entity into account when planning, evaluating, or determining a route.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:07 a.m.