Triple
T24127894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ampersand Mountain |
E597858
|
entity |
| Predicate | trailSteepness |
P24163
|
FINISHED |
| Object | relatively short but steep |
—
|
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: relatively short but steep | Statement: [Ampersand Mountain, trailSteepness, relatively short but steep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailSteepness Context triple: [Ampersand Mountain, trailSteepness, relatively short but steep]
-
A.
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.
-
B.
hasTrailDifficulty
chosen
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
C.
isMountainRoad
Indicates that a given road is classified as a mountain road, typically traversing or situated within mountainous terrain.
-
D.
slopeType
Indicates the classification of a slope based on its geometric or physical characteristics, such as steepness, shape, or orientation.
-
E.
slopeAspect
Indicates the compass direction that a slope or surface is facing.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df740a508190a80af01d99000127 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:21 p.m.