Triple
T25399384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanserhorn |
E636377
|
entity |
| Predicate | hasOldestSectionOfFunicular |
P158266
|
FINISHED |
| Object | opened 1893 |
—
|
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: opened 1893 | Statement: [Stanserhorn, hasOldestSectionOfFunicular, opened 1893]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldestSectionOfFunicular Context triple: [Stanserhorn, hasOldestSectionOfFunicular, opened 1893]
-
A.
isOldestFunicularIn
Indicates that a funicular is the most ancient or earliest-established funicular within a specified location or region.
-
B.
hasFunicular
Indicates that one place or facility is equipped with or served by a funicular railway connection to another location.
-
C.
funicularOpeningDate
Indicates the calendar date on which a funicular railway was first opened for operation.
-
D.
funicularRailwayName
Indicates that a funicular railway has the specified name.
-
E.
hasCableCar
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
- F. None of above. chosen
Provenance (4 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f8802c819085d55049bd94b075 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:50 p.m.