Triple
T7545802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Findel Glacier |
E178398
|
entity |
| Predicate | hasViewOf |
P854
|
FINISHED |
| Object | Täschhorn |
E186331
|
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: Täschhorn | Statement: [Findel Glacier, hasViewOf, Täschhorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Täschhorn Context triple: [Findel Glacier, hasViewOf, Täschhorn]
-
A.
Täschhorn
chosen
Täschhorn is a prominent 4,491-meter alpine peak in the Swiss canton of Valais, known for its steep faces and challenging climbing routes near the Matterhorn.
-
B.
Lauteraarhorn
Lauteraarhorn is a prominent, steep pyramidal peak in the Swiss Bernese Alps, known for its challenging climbs and striking glaciated surroundings.
-
C.
Finsteraarhorn
Finsteraarhorn is a prominent, glaciated peak in the Swiss Alps known for its remote location and striking pyramidal shape.
-
D.
Oeschinenhorn
Oeschinenhorn is a prominent peak in the Bernese Alps of Switzerland, forming part of the Blüemlisalp massif and known for its rugged alpine terrain and mountaineering routes.
-
E.
Aletschhorn
Aletschhorn is a prominent high peak in the Swiss Alps known for its extensive glaciation and challenging alpine climbs.
- 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_69c856b93188819080c769a2a1b122f4 |
completed | March 28, 2026, 10:31 p.m. |
Created at: March 27, 2026, 3:48 p.m.