Triple
T34276118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenmacnass Valley |
E879459
|
entity |
| Predicate | viewpointAt |
P127904
|
FINISHED |
| Object | car park above Glenmacnass Waterfall |
—
|
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: car park above Glenmacnass Waterfall | Statement: [Glenmacnass Valley, viewpointAt, car park above Glenmacnass Waterfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewpointAt Context triple: [Glenmacnass Valley, viewpointAt, car park above Glenmacnass Waterfall]
-
A.
viewpointFrom
Indicates a relationship where something is observed, depicted, or described from the perspective or location of a particular entity or point.
-
B.
viewpointNear
Indicates that one entity serves as a viewpoint or vantage location that is geographically close to another entity.
-
C.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
D.
hasViewingPointFor
chosen
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
E.
locationOfVision
Indicates the place or setting where a vision or visual experience occurs or is perceived.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.