Triple
T34593341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederiksberg Station |
E888244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Copenhagen Metro station |
C59994
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Copenhagen Metro station Context triple: [Frederiksberg Station, instanceOf, Copenhagen Metro station]
-
A.
Copenhagen S-train station
A Copenhagen S-train station is a designated rail facility within the Copenhagen S-train network where passengers can board, alight, and transfer between frequent suburban and urban train services.
-
B.
S-train station
An S-train station is a designated stop or terminal along an urban or suburban S-train network where passengers can board, alight, and transfer between trains and other modes of public transportation.
-
C.
Oslo Metro station
An Oslo Metro station is a designated stop along the Oslo Metro network where trains load and unload passengers, typically featuring platforms, ticketing facilities, signage, and connections to other modes of public transport.
-
D.
Stockholm metro station
A Stockholm metro station is a designated stop within Stockholm's rapid transit system where passengers can board, alight, and transfer between metro trains, often featuring distinctive architectural or artistic designs.
-
E.
Helsinki Metro station
A Helsinki Metro station is a designated stop along the Helsinki Metro system where trains load and unload passengers, typically featuring platforms, ticketing facilities, signage, and connections to other modes of public transport.
- F. None of above. chosen
Provenance (1 batch)
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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.