Triple
T8004546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Täschhorn |
E186331
|
entity |
| Predicate | hasGlacier |
P4580
|
FINISHED |
| Object | Feegletscher |
E430962
|
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: Feegletscher | Statement: [Täschhorn, hasGlacier, Feegletscher]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Feegletscher Context triple: [Täschhorn, hasGlacier, Feegletscher]
-
A.
Feegletscher
chosen
Feegletscher is a prominent alpine glacier in the Swiss canton of Valais, lying above the resort village of Saas-Fee in the Pennine Alps.
-
B.
Festigletscher
Festigletscher is a glacier located on the slopes of the Dom, one of the highest peaks in the Swiss Alps.
-
C.
Rimpfischgletscher
Rimpfischgletscher is a mountain glacier in the Pennine Alps of Valais, Switzerland, lying on the flanks of the Rimpfischhorn between Zermatt and Saas-Fee.
-
D.
Mellichgletscher
Mellichgletscher is a glacier on the slopes of the Rimpfischhorn in the Pennine Alps of Switzerland.
-
E.
Fletschhorn Glacier
Fletschhorn Glacier is an alpine glacier located on the slopes of the Fletschhorn mountain in the Pennine Alps of Switzerland.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf5fb588190ada4ec7d8087619c |
completed | March 31, 2026, 3:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc93a132c08190bc9a00667aa32b90 |
completed | April 1, 2026, 3:40 a.m. |
Created at: March 30, 2026, 5:18 p.m.