Triple
T7875835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrisa |
E182848
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Klosters |
E705882
|
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: Klosters | Statement: [Madrisa, locatedNear, Klosters]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Klosters Context triple: [Madrisa, locatedNear, Klosters]
-
A.
Klosters
chosen
Klosters is a renowned Swiss Alpine village and ski resort in the canton of Graubünden, popular for its picturesque scenery and winter sports.
-
B.
Kandersteg
Kandersteg is a Swiss mountain village and popular tourist resort known for its scenic alpine landscapes, hiking trails, and access to Lake Oeschinen.
-
C.
Arosa
Arosa is a Swiss alpine resort town in the canton of Graubünden, known for its skiing, hiking, and scenic mountain landscapes.
-
D.
Wengen
Wengen is a car-free Swiss alpine village and popular ski and hiking resort located in the Bernese Oberland region.
-
E.
Andermatt
Andermatt is a Swiss Alpine village and ski resort in the canton of Uri, known as a major mountain transport hub and tourist destination.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39aa7ca88190b88a18f6a8971e51 |
completed | March 31, 2026, 3:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd33b7c0c48190bc3c1b97aee0b741 |
completed | April 1, 2026, 3:03 p.m. |
Created at: March 30, 2026, 4:57 p.m.