Triple
T15302253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preikestolen |
E365816
|
entity |
| Predicate | hikeElevationGain |
P30489
|
FINISHED |
| Object | about 330 metres |
—
|
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: about 330 metres | Statement: [Preikestolen, hikeElevationGain, about 330 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hikeElevationGain Context triple: [Preikestolen, hikeElevationGain, about 330 metres]
-
A.
elevationGainFunction
Indicates a functional relationship that maps a path, route, or movement to the total amount of elevation gained along it.
-
B.
hasApproxElevationGainFt
Indicates that one entity is associated with an approximate amount of elevation gain, measured in feet, relative to another context or reference.
-
C.
elevationGainRelativeToBase
Indicates the amount of elevation increase of something compared to a defined base level.
-
D.
totalAscent
chosen
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
E.
hikeLength
Indicates the distance or duration associated with a hiking activity or trail.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccd575c8190aa43262d3b73ef3c |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.