Triple
T15302288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kjerag |
E365817
|
entity |
| Predicate | knownFor |
P22
|
FINISHED |
| Object | Kjeragbolten |
E365817
|
NE 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: Kjeragbolten | Statement: [Kjerag, knownFor, Kjeragbolten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kjeragbolten Context triple: [Kjerag, knownFor, Kjeragbolten]
-
A.
Kjerag
chosen
Kjerag is a famous mountain in Norway’s Lysefjord known for its towering cliffs, popular hiking routes, and the iconic Kjeragbolten boulder wedged between two rock faces.
-
B.
Spiterstulen
Spiterstulen is a mountain lodge in Norway’s Jotunheimen region that serves as a key base for hikers and climbers exploring nearby peaks.
-
C.
Kjerkeberget
Kjerkeberget is a forested hill in Norway that marks the highest natural point within Oslo’s municipal boundaries.
-
D.
Bandåsen
Bandåsen is the highest peak on the island of Ombo in Norway.
-
E.
Tallkrogen
Tallkrogen is a residential district in southern Stockholm, Sweden, known for its small-scale housing and garden-city character.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef86b8cc81909969098b1766f6b7 |
completed | May 9, 2026, 8:25 a.m. |
Created at: April 10, 2026, 3:15 a.m.