Triple
T30607777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichenbach Falls |
E779091
|
entity |
| Predicate | funicularName |
P62713
|
FINISHED |
| Object | Reichenbachfall Funicular |
—
|
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: Reichenbachfall Funicular | Statement: [Reichenbach Falls, funicularName, Reichenbachfall Funicular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funicularName Context triple: [Reichenbach Falls, funicularName, Reichenbachfall Funicular]
-
A.
funicularRailwayName
chosen
Indicates that a funicular railway has the specified name.
-
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.
isOldestFunicularIn
Indicates that a funicular is the most ancient or earliest-established funicular within a specified location or region.
-
E.
funicularLowerStationLocatedIn
Indicates that the lower (downhill) station of a funicular railway is located within a specified place or area.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b705108190a8e24035079b3948 |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.