Triple
T31558777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brecon Canal Basin |
E805200
|
entity |
| Predicate | isScenicStartingPointFor |
P171962
|
FINISHED |
| Object | canal-side walks |
—
|
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: canal-side walks | Statement: [Brecon Canal Basin, isScenicStartingPointFor, canal-side walks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScenicStartingPointFor Context triple: [Brecon Canal Basin, isScenicStartingPointFor, canal-side walks]
-
A.
isScenicAlternativeTo
Indicates that one route, path, or option serves as an alternative to another while offering more visually appealing or picturesque surroundings.
-
B.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
C.
isPartOfScenicVista
Indicates that something is included within, or contributes to, a larger scenic vista or panoramic view.
-
D.
hasScenicViewOf
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
E.
hasScenicAccessTo
Indicates that one place or object provides a visually appealing or notable view of another place or object.
- F. None of above. chosen
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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:14 p.m.