Triple
T21018544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zernez |
E517741
|
entity |
| Predicate | hasNearbyAttraction |
P2064
|
FINISHED |
| Object | Ofen Pass |
—
|
NE NERFINISHED |
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: Ofen Pass | Statement: [Zernez, hasNearbyAttraction, Ofen Pass]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ofen Pass Context triple: [Zernez, hasNearbyAttraction, Ofen Pass]
-
A.
Ofen Pass
chosen
Ofen Pass is a high mountain pass in the Swiss canton of Graubünden that connects the Engadine valley with the Val Müstair through the Rhaetian Alps.
-
B.
Loibl Pass
Loibl Pass is a mountain pass in the Karawanks range that connects Austria and Slovenia, historically serving as an important transalpine route.
-
C.
Thurn Pass
Thurn Pass is a mountain pass in the Kitzbühel Alps of Austria, serving as an important route through this alpine region.
-
D.
Albis Pass
Albis Pass is a mountain pass in the Albis range of the Swiss canton of Zurich, serving as a scenic route and local transport link between the Sihl Valley and the Reuss Valley.
-
E.
Roki Pass
Roki Pass is a high mountain pass in the Greater Caucasus that serves as a key transit route between Georgia and Russia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5a27f08190b26828a6a7b59f7c |
completed | April 21, 2026, 4:26 a.m. |
Created at: April 16, 2026, 1:54 p.m.