Triple
T10542714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llyn Ogwen |
E248735
|
entity |
| Predicate | nearTrailheadFor |
P11755
|
FINISHED |
| Object | Tryfan north ridge routes |
—
|
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: Tryfan north ridge routes | Statement: [Llyn Ogwen, nearTrailheadFor, Tryfan north ridge routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearTrailheadFor Context triple: [Llyn Ogwen, nearTrailheadFor, Tryfan north ridge routes]
-
A.
hasNearbyTrailheadFor
chosen
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
B.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
-
C.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
-
D.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
-
E.
nearestHut
Indicates that one hut is the closest in distance to a given reference point or entity compared to all other huts.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5190f46d08190a92b1191881ffb92 |
completed | April 7, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:32 p.m.