Triple
T17894808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VR Group |
E447404
|
entity |
| Predicate | railNetworkCoverage |
P124547
|
FINISHED |
| Object | nationwide in Finland |
—
|
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: nationwide in Finland | Statement: [VR Group, railNetworkCoverage, nationwide in Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railNetworkCoverage Context triple: [VR Group, railNetworkCoverage, nationwide in Finland]
-
A.
railroadNetwork
Indicates a relationship where locations are connected as part of the same system of railway lines and infrastructure used for train transport.
-
B.
railNetworkCenter
Indicates that a location functions as a central hub or focal point within a rail transportation network.
-
C.
appliesToRailwayNetwork
chosen
Indicates that something is relevant or specifically applicable to a railway network as a whole.
-
D.
railwayNetworkLength
Indicates the total measured length of all railway tracks within a specified railway network.
-
E.
railInfrastructureServed
Indicates that a rail infrastructure facility or segment is served, accessed, or operated by a particular service, operator, or network.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7ccf808190b4c1fd477043bcc8 |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.