Triple
T29578010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kampenwand |
E753496
|
entity |
| Predicate | cableCarUpperStation |
P116922
|
FINISHED |
| Object | near Steinlingalm |
—
|
LITERAL 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: near Steinlingalm | Statement: [Kampenwand, cableCarUpperStation, near Steinlingalm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cableCarUpperStation Context triple: [Kampenwand, cableCarUpperStation, near Steinlingalm]
-
A.
cableCarStations
Indicates that there is a cable car connection or service operating between the referenced stations.
-
B.
upperStation
Indicates that one station is positioned higher or upstream in a system or hierarchy relative to another station.
-
C.
cableCarOpened
Indicates that a cable car system or line has begun operating or was officially opened for use.
-
D.
upperStationLocatedOn
chosen
Indicates that one station in a pair (the upper station) is situated at the higher or top position along a route, line, or system relative to another station.
-
E.
cableCarSystem
Indicates a relationship where a transportation system operates vehicles pulled by cables along fixed routes, typically on steep gradients.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:04 p.m.