Triple
T18107707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuscherkarkopf |
E433386
|
entity |
| Predicate | normalRouteFrom |
P32243
|
FINISHED |
| Object | Fuscher Törl |
—
|
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: Fuscher Törl | Statement: [Fuscherkarkopf, normalRouteFrom, Fuscher Törl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fuscher Törl Context triple: [Fuscherkarkopf, normalRouteFrom, Fuscher Törl]
-
A.
Fuscher Törl
chosen
Fuscher Törl is a high mountain pass and scenic viewpoint in the Austrian Alps, known for its panoramic vistas along the Grossglockner High Alpine Road.
-
B.
Zoettl
Zoettl is the surname of Brother Joseph Zoettl, a Benedictine monk known for creating the Ave Maria Grotto in Alabama.
-
C.
Fiser
Fiser is a surname variant of Fischer, commonly associated with Central or Eastern European origins.
-
D.
Luchsinger
Luchsinger is a Swiss surname of Germanic origin, borne by various notable individuals including mountaineers and public figures.
-
E.
Fuscherkarkopf
Fuscherkarkopf is a prominent alpine peak in the Austrian Alps, known for its high elevation and location within the Glockner Group of the Hohe Tauern range.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbb3d408190b5fc7870bc6512f4 |
completed | April 19, 2026, 1:50 p.m. |
Created at: April 10, 2026, 10:28 a.m.