Triple
T28116554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niesen |
E710648
|
entity |
| Predicate | funicularUpperStationLocatedAt |
P116922
|
FINISHED |
| Object | Niesen Kulm |
—
|
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: Niesen Kulm | Statement: [Niesen, funicularUpperStationLocatedAt, Niesen Kulm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funicularUpperStationLocatedAt Context triple: [Niesen, funicularUpperStationLocatedAt, Niesen Kulm]
-
A.
funicularLowerStationLocatedIn
Indicates that the lower (downhill) station of a funicular railway is located within a specified place or area.
-
B.
funicularRailwayName
Indicates that a funicular railway has the specified name.
-
C.
upperStationLocatedOn
chosen
Indicates that one station in a pair (the upper station) is situated at the higher or top position along a route, line, or system relative to another station.
-
D.
funicularOpeningDate
Indicates the calendar date on which a funicular railway was first opened for operation.
-
E.
hasFunicular
Indicates that one place or facility is equipped with or served by a funicular railway connection to another location.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 9:14 p.m.