Triple
T4787936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelboden |
E106528
|
entity |
| Predicate | hasAttraction |
P105
|
FINISHED |
| Object | Sillerenbühl |
E468794
|
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: Sillerenbühl | Statement: [Adelboden, hasAttraction, Sillerenbühl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sillerenbühl Context triple: [Adelboden, hasAttraction, Sillerenbühl]
-
A.
Sunnbüel
chosen
Sunnbüel is a high-altitude alpine plateau and hiking area in the Bernese Oberland region of Switzerland, known for its scenic mountain landscapes and outdoor activities.
-
B.
Bettlach
Bettlach is a Swiss municipality located in the canton of Solothurn.
-
C.
Lommersweiler
Lommersweiler is a village and municipal section of the town of St. Vith in the German-speaking Community of eastern Belgium.
-
D.
Sihltal
Sihltal is a Swiss valley in the canton of Zurich shaped by the Sihl River, known for its scenic landscapes and proximity to the city of Zurich.
-
E.
Riederfurka
Riederfurka is a mountain pass and viewpoint in the Swiss Alps, known for its access to hiking and skiing routes with panoramic views of the Aletsch Glacier.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65da229c81909c703393f7b9b71d |
completed | March 20, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be4d93f2cc8190acf96766d2c5a946 |
completed | March 21, 2026, 7:49 a.m. |
Created at: March 20, 2026, 1:22 p.m.