Triple
T20018506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trollstigen |
E494784
|
entity |
| Predicate | hasMaximumSteepness |
P46516
|
FINISHED |
| Object | 10% gradient |
—
|
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: 10% gradient | Statement: [Trollstigen, hasMaximumSteepness, 10% gradient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumSteepness Context triple: [Trollstigen, hasMaximumSteepness, 10% gradient]
-
A.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
-
B.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
-
C.
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.
-
D.
maximumGradient
chosen
Indicates the greatest rate of change or steepest slope that occurs within a given function, surface, or dataset.
-
E.
hasSettlementOnSlopes
Indicates that a settlement is located on or extends across the slopes of a landform such as a hill or mountain.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623e40748190b1abb0ead9acab4e |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.