Triple
T29130053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piz Medel |
E738346
|
entity |
| Predicate | hasNormalRouteFrom |
P4374
|
FINISHED |
| Object | Medelserhütte SAC |
—
|
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: Medelserhütte SAC | Statement: [Piz Medel, hasNormalRouteFrom, Medelserhütte SAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNormalRouteFrom Context triple: [Piz Medel, hasNormalRouteFrom, Medelserhütte SAC]
-
A.
hasRoute
chosen
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasRouteDestination
Indicates that a route leads to or terminates at a specified destination.
-
C.
hasCommonRoute
Indicates that two or more entities share at least one overlapping or identical route or path.
-
D.
hasNavigationRoute
Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
-
E.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
- F. None of above.
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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: April 28, 2026, 11:31 a.m.