Triple
T26072041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grisedale valley |
E657575
|
entity |
| Predicate | hasFootpathTo |
P90518
|
FINISHED |
| Object | Grisedale Tarn |
E1712012
|
NE 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: Grisedale Tarn | Statement: [Grisedale valley, hasFootpathTo, Grisedale Tarn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootpathTo Context triple: [Grisedale valley, hasFootpathTo, Grisedale Tarn]
-
A.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
B.
hasPathway
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
-
C.
hasWalkingRouteConnection
chosen
Indicates that there is a walkable path or route directly connecting two locations.
-
D.
hasFootways
Indicates that something includes or is connected to designated footpaths or pedestrian walkways.
-
E.
hasStepsLeadingTo
Indicates that one location or object is connected to another by a set of steps or a staircase leading toward it.
- F. None of above.
Provenance (4 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11856059bc81909dd1eef6799631f3 |
completed | May 23, 2026, 10:45 a.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 26, 2026, 7:30 p.m.