Triple
T33516348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotwand |
E858375
|
entity |
| Predicate | hasCableCarAccessNearby |
P195188
|
FINISHED |
| Object | Taubensteinbahn |
—
|
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: Taubensteinbahn | Statement: [Rotwand, hasCableCarAccessNearby, Taubensteinbahn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCableCarAccessNearby Context triple: [Rotwand, hasCableCarAccessNearby, Taubensteinbahn]
-
A.
hasCableCarLineNearby
chosen
Indicates that there is at least one cable car line located in close proximity to the referenced entity.
-
B.
hasCableCar
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
-
C.
hasAerialTram
Indicates that one entity possesses or is served by an aerial tramway connection.
-
D.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
E.
hasSkiLiftConnectionTo
Indicates a relationship where one location is directly connected to another by a ski lift, allowing travel between them via that lift.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, 1:39 a.m.