Triple
T34140919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helagsfjället |
E875714
|
entity |
| Predicate | nearestMountainStation |
P84030
|
FINISHED |
| Object | Helags Mountain Station |
—
|
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: Helags Mountain Station | Statement: [Helagsfjället, nearestMountainStation, Helags Mountain Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMountainStation Context triple: [Helagsfjället, nearestMountainStation, Helags Mountain Station]
-
A.
upperStationElevation
Indicates the elevation or height above a reference level (e.g., sea level) of the upper station in a system or structure.
-
B.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
-
C.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
D.
hasMountainStation
chosen
Indicates that an entity possesses or is associated with a station located in a mountainous area.
-
E.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:54 a.m.