Triple
T18212710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starý Smokovec |
E436072
|
entity |
| Predicate | hasCableway |
P43180
|
FINISHED |
| Object | funicular to Hrebienok |
—
|
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: funicular to Hrebienok | Statement: [Starý Smokovec, hasCableway, funicular to Hrebienok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCableway Context triple: [Starý Smokovec, hasCableway, funicular to Hrebienok]
-
A.
hasCableCar
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
-
B.
hasFunicular
chosen
Indicates that one place or facility is equipped with or served by a funicular railway connection to another location.
-
C.
cablewayType
Indicates the specific kind or classification of a cableway system associated with an entity.
-
D.
cableCarSystem
Indicates a relationship where a transportation system operates vehicles pulled by cables along fixed routes, typically on steep gradients.
-
E.
cableCarStations
Indicates that there is a cable car connection or service operating between the referenced stations.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e22a26308190a6720b41a9bbfc2d |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.