Triple
T30187478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochaber ski area |
E767375
|
entity |
| Predicate | accessesSlopeOf |
P83773
|
FINISHED |
| Object | Aonach Mòr |
—
|
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: Aonach Mòr | Statement: [Lochaber ski area, accessesSlopeOf, Aonach Mòr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesSlopeOf Context triple: [Lochaber ski area, accessesSlopeOf, Aonach Mòr]
-
A.
isOnSlopeOf
chosen
Indicates that one entity is located on the inclined surface or side of another entity, typically a sloping terrain or structure.
-
B.
hasSlopeRating
Indicates that something (typically a golf course or hole) is associated with a specific slope rating value that quantifies its relative difficulty for bogey golfers compared to scratch golfers.
-
C.
hasSlopeFeature
Indicates that an entity possesses or is characterized by a particular slope-related property or feature.
-
D.
usesIntermediateSlope
Indicates that an entity employs or operates on a slope of intermediate steepness as part of its process or behavior.
-
E.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 7:27 p.m.