Triple
T5482750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gubałówka Hill |
E123504
|
entity |
| Predicate | transportTypeToSummit |
P1379
|
FINISHED |
| Object | funicular railway |
—
|
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 railway | Statement: [Gubałówka Hill, transportTypeToSummit, funicular railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportTypeToSummit Context triple: [Gubałówka Hill, transportTypeToSummit, funicular railway]
-
A.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
C.
summitAccessibleFrom
Indicates that a summit can be reached or accessed starting from a specified location or route.
-
D.
transportModeIntegration
Indicates that different modes of transportation are coordinated or combined to enable seamless or efficient movement within a journey or transport system.
-
E.
typicalTransportBetweenPeaks
Indicates the usual or most common mode of transportation used to travel between two peaks.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.