Triple
T4971615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gstaad |
E111663
|
entity |
| Predicate | hasNearbyResort |
P3449
|
FINISHED |
| Object | Saanenmöser |
E483742
|
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: Saanenmöser | Statement: [Gstaad, hasNearbyResort, Saanenmöser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saanenmöser Context triple: [Gstaad, hasNearbyResort, Saanenmöser]
-
A.
Oberegg
Oberegg is a Swiss municipality in the canton of Appenzell Innerrhoden, known for its rural landscape and location in the Appenzell region.
-
B.
Ruetz
Ruetz is a river in the Stubai Valley of Tyrol, Austria, known for its alpine course through the Stubai Alps before joining the Sill River.
-
C.
Saanen
chosen
Saanen is a picturesque Swiss village in the Bernese Oberland known for its traditional chalets, alpine scenery, and proximity to the upscale resort town of Gstaad.
-
D.
Bettlach
Bettlach is a Swiss municipality located in the canton of Solothurn.
-
E.
Gimmelwald
Gimmelwald is a small, traditional Swiss alpine village known for its dramatic mountain scenery and tranquil, car-free atmosphere in the Bernese Oberland.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7214e18c81909db1c838a4cce78d |
completed | March 20, 2026, 4:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be89fddbb8819084c8c21ee0ce845e |
completed | March 21, 2026, 12:07 p.m. |
Created at: March 20, 2026, 1:33 p.m.