Triple
T5174116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jungfrau |
E116753
|
entity |
| Predicate | visibleFrom |
P1165
|
FINISHED |
| Object | Mürren |
E102976
|
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: Mürren | Statement: [Jungfrau, visibleFrom, Mürren]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mürren Context triple: [Jungfrau, visibleFrom, Mürren]
-
A.
Mürren
chosen
Mürren is a traditional, car-free mountain village and popular ski resort perched high above the Lauterbrunnen Valley in the Swiss Bernese Alps.
-
B.
Wengen
Wengen is a car-free Swiss alpine village and popular ski and hiking resort located in the Bernese Oberland region.
-
C.
Gimmelwald
Gimmelwald is a small, traditional Swiss alpine village known for its dramatic mountain scenery and tranquil, car-free atmosphere in the Bernese Oberland.
-
D.
Adelboden
Adelboden is a Swiss alpine village and ski resort in the Bernese Oberland, known for its mountain scenery and World Cup ski races.
-
E.
Kandersteg
Kandersteg is a Swiss mountain village and popular tourist resort known for its scenic alpine landscapes, hiking trails, and access to Lake Oeschinen.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd796f7c308190a721e33aabd499ac |
completed | March 20, 2026, 4:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bee07a6620819089e2b3fcb322a47e |
completed | March 21, 2026, 6:16 p.m. |
Created at: March 20, 2026, 1:45 p.m.