Triple
T7545803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Findel Glacier |
E178398
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Rimpfischhorn |
E162481
|
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: Rimpfischhorn | Statement: [Findel Glacier, hasViewOf, Rimpfischhorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rimpfischhorn Context triple: [Findel Glacier, hasViewOf, Rimpfischhorn]
-
A.
Rimpfischhorn
chosen
Rimpfischhorn is a prominent high-altitude mountain in the Swiss Pennine Alps, known for its glaciated slopes and challenging climbing routes.
-
B.
Stecknadelhorn
Stecknadelhorn is a high alpine peak in the Pennine Alps of Switzerland, known as one of the prominent summits of the Mischabel range.
-
C.
Nadelhorn
Nadelhorn is a prominent 4,000-meter-class peak in the Swiss Alps, known for its sharp, needle-like summit and popular alpine climbing routes.
-
D.
Fletschhorn
Fletschhorn is a prominent mountain peak in the Swiss Pennine Alps, known for its glaciated slopes and popularity among alpine climbers.
-
E.
Wiesbachhorn
Wiesbachhorn is a prominent alpine peak in the Austrian Alps, known for its impressive height and glaciated slopes within the Hohe Tauern range.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f89963ec8190ae7b8a2b9508c074 |
completed | March 27, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c84f21aa5c819085e8d1ecbd9b01e3 |
completed | March 28, 2026, 9:58 p.m. |
Created at: March 27, 2026, 3:48 p.m.