Triple
T24990158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hochtor Pass |
E625422
|
entity |
| Predicate | roadMaximumGradient |
P157514
|
FINISHED |
| Object | steep alpine gradients |
—
|
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: steep alpine gradients | Statement: [Hochtor Pass, roadMaximumGradient, steep alpine gradients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadMaximumGradient Context triple: [Hochtor Pass, roadMaximumGradient, steep alpine gradients]
-
A.
railwayGradient
Indicates the slope or steepness of a railway track along its route.
-
B.
maximumGradient
Indicates the greatest rate of change or steepest slope that occurs within a given function, surface, or dataset.
-
C.
roadAverageGradientFromBédoin
Indicates the average slope or steepness of the road when ascending from Bédoin.
-
D.
railroadGrade
Indicates that one entity is at the elevation or level of a railroad track or crossing relative to another entity.
-
E.
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.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a4416e881909c58f3b4d9e4b42d |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:03 a.m.