Triple
T747721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernese Alps |
E15379
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Jungfraujoch |
E116753
|
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: Jungfraujoch | Statement: [Bernese Alps, contains, Jungfraujoch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jungfraujoch Context triple: [Bernese Alps, contains, Jungfraujoch]
-
A.
Jungfrau
chosen
Jungfrau is a prominent and picturesque mountain peak in the Swiss Alps, renowned for its dramatic scenery and status as part of a UNESCO World Heritage Site.
-
B.
Zugspitze
Zugspitze is the highest mountain in Germany, located in the Bavarian Alps near the Austrian border.
-
C.
Finsteraarhorn
Finsteraarhorn is a prominent, glaciated peak in the Swiss Alps known for its remote location and striking pyramidal shape.
-
D.
Schreckhorn
Schreckhorn is a prominent and rugged mountain peak in the Swiss Alps, known for its challenging climbs and striking glaciated scenery.
-
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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62dd1bc819094a3814654448ae3 |
completed | March 1, 2026, 8:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac598bddf88190afc565deec2357a1 |
completed | March 7, 2026, 4:59 p.m. |
Created at: March 1, 2026, 7:37 p.m.