Triple
T33222777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walchensee |
E850467
|
entity |
| Predicate | nearbyMountainRailway |
P195188
|
FINISHED |
| Object | Herzogstandbahn cable car |
—
|
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: Herzogstandbahn cable car | Statement: [Walchensee, nearbyMountainRailway, Herzogstandbahn cable car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMountainRailway Context triple: [Walchensee, nearbyMountainRailway, Herzogstandbahn cable car]
-
A.
hasMountainRailwayConnectionTo
Indicates that there is a railway line specifically adapted for mountainous terrain that connects one location to another.
-
B.
nearbyHillStation
Indicates that one location is a hill station situated close to another specified place.
-
C.
hasCableCarLineNearby
chosen
Indicates that there is at least one cable car line located in close proximity to the referenced entity.
-
D.
nearbyMountainRegion
Indicates that one location is situated close to or within the surrounding area of a mountainous region.
-
E.
nearestMajorTrekkingHub
Indicates the closest significant trekking center or hub associated with a given location.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 1, 2026, 1:30 a.m.