Triple
T31714006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebelhorn cable car |
E809404
|
entity |
| Predicate | hasTopStationElevation |
P102982
|
FINISHED |
| Object | approximately 2224 m |
—
|
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: approximately 2224 m | Statement: [Nebelhorn cable car, hasTopStationElevation, approximately 2224 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopStationElevation Context triple: [Nebelhorn cable car, hasTopStationElevation, approximately 2224 m]
-
A.
hasTopElevation
Indicates that an entity has a specified maximum or highest elevation value.
-
B.
upperStationElevation
chosen
Indicates the elevation or height above a reference level (e.g., sea level) of the upper station in a system or structure.
-
C.
hasValleyStationElevation
Indicates the elevation at which the valley station associated with something is located.
-
D.
hasAltitudeStation
Indicates that something is associated with or located at a station characterized by a specific altitude.
-
E.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 30, 2026, 11:16 p.m.