Triple
T18904972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höllentalbahn |
E462435
|
entity |
| Predicate | isScenicRailway |
P97408
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Höllentalbahn, isScenicRailway, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScenicRailway Context triple: [Höllentalbahn, isScenicRailway, true]
-
A.
hasScenicPassNearby
Indicates that a location is situated close to a notable scenic pass, such as a mountain or landscape viewpoint route.
-
B.
isScenicStopOn
Indicates that a location serves as a designated scenic viewpoint or attraction situated along a particular route or path.
-
C.
Scenic RailwayStatus
chosen
Indicates that an entity’s status or condition is specifically related to a scenic railway (e.g., whether it is active, inactive, under construction, or otherwise classified).
-
D.
hasRailroadAttraction
Indicates that one entity features or contains a railroad-related attraction, such as a railway exhibit, ride, or point of interest.
-
E.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52c121c8190a2057b99c723694b |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.