Triple
T15216552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fløibanen |
E363650
|
entity |
| Predicate | operator |
P179
|
FINISHED |
| Object | Fløibanen AS |
E1143513
|
NE 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: Fløibanen AS | Statement: [Fløibanen, operator, Fløibanen AS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fløibanen AS Context triple: [Fløibanen, operator, Fløibanen AS]
-
A.
Fløibanen AS
chosen
Fløibanen AS is the company that operates the Fløibanen funicular railway in Bergen, Norway.
-
B.
Norwegian State Railways
Norwegian State Railways was Norway’s former government-owned railway company responsible for most passenger train services and rail operations across the country.
-
C.
Oslo Sporveier
Oslo Sporveier was the former municipal public transport operator in Oslo, Norway, responsible for running the city’s trams, buses, and metro services.
-
D.
Bergensbanen
Bergensbanen is a famous Norwegian railway line that traverses dramatic mountain landscapes between Bergen and Oslo, often regarded as one of the most scenic train routes in Europe.
-
E.
Kongsvinger Line
The Kongsvinger Line is a Norwegian railway route running east from Oslo toward the Swedish border, serving both passenger and freight traffic.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076f90c481909989befe031a2cae |
completed | April 15, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fedd3159fc81908c05cfbd0bd7e5ac |
completed | May 9, 2026, 7:07 a.m. |
Created at: April 10, 2026, 3:11 a.m.