Triple
T28159536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arosa |
E714851
|
entity |
| Predicate | terminusOfRailwayLine |
P26272
|
FINISHED |
| Object | Chur–Arosa railway line |
—
|
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: Chur–Arosa railway line | Statement: [Arosa, terminusOfRailwayLine, Chur–Arosa railway line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusOfRailwayLine Context triple: [Arosa, terminusOfRailwayLine, Chur–Arosa railway line]
-
A.
railwayUpperTerminus
Indicates that a railway line or route reaches its upper (typically higher-altitude or upstream) terminal endpoint at the related location.
-
B.
railLineTerminus
chosen
Indicates that a rail line ends or terminates at the specified location or station.
-
C.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
D.
formerTerminalStation
Indicates that a location once served as the end point (terminus) of a transportation line or route but no longer holds that status.
-
E.
railTerminusFor
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 10:05 p.m.