Triple
T8857608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höllental |
E210797
|
entity |
| Predicate | hasRouteTo |
P4374
|
FINISHED |
| Object | Zugspitze |
E41130
|
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: Zugspitze | Statement: [Höllental, hasRouteTo, Zugspitze]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zugspitze Context triple: [Höllental, hasRouteTo, Zugspitze]
-
A.
Zugspitze
chosen
Zugspitze is the highest mountain in Germany, located in the Bavarian Alps near the Austrian border.
-
B.
Königspitze
Königspitze is a prominent high peak in the Eastern Alps of northern Italy, renowned among mountaineers for its steep faces and challenging climbing routes.
-
C.
Schneefernerkopf
Schneefernerkopf is a prominent peak in the Bavarian Alps near Germany’s highest mountain, Zugspitze, known for its rugged terrain and alpine scenery.
-
D.
Lenzspitze
Lenzspitze is a prominent high-altitude peak in the Swiss Pennine Alps, known for its sharp ridges and challenging alpine climbing routes.
-
E.
Watzmann
Watzmann is a prominent mountain massif in the Bavarian Alps, renowned for its striking peaks and dramatic presence above the town of Berchtesgaden.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e3b62c8190bf779e7e1db767f6 |
completed | April 1, 2026, 12:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfeb1d130c81909f7f23b7ad8bba9f |
completed | April 3, 2026, 4:30 p.m. |
Created at: March 30, 2026, 6:50 p.m.