Triple
T7922328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davos Dorf railway station |
E183973
|
entity |
| Predicate | hasAltitudeCategory |
P35392
|
FINISHED |
| Object | alpine station |
—
|
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: alpine station | Statement: [Davos Dorf railway station, hasAltitudeCategory, alpine station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAltitudeCategory Context triple: [Davos Dorf railway station, hasAltitudeCategory, alpine station]
-
A.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
B.
altitudeCategory
chosen
Indicates the classification of something based on its height or elevation relative to a reference level (e.g., low, medium, high altitude).
-
C.
hasCliffHeightCategory
Indicates the categorized height range of a cliff associated with an entity.
-
D.
hasAltitudeStation
Indicates that something is associated with or located at a station characterized by a specific altitude.
-
E.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a9499cc8190b6bd81f4625c77ab |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:06 p.m.