Triple

T22752649
Position Surface form Disambiguated ID Type / Status
Subject Vy Gjøvikbanen E562745 entity
Predicate railwayOperatorFor P121930 FINISHED
Object passenger services on the Gjøvik Line 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: passenger services on the Gjøvik Line | Statement: [Vy Gjøvikbanen, railwayOperatorFor, passenger services on the Gjøvik Line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railwayOperatorFor
Context triple: [Vy Gjøvikbanen, railwayOperatorFor, passenger services on the Gjøvik Line]
  • A. hasRailTransportOperator chosen
    Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
  • B. railwayCompanyOnRoute
    Indicates that a particular railway company operates or provides service on a specified route.
  • C. railwayCompany
    Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
  • D. formerRailOperator
    Indicates that an entity previously operated a rail service or railway system but no longer does so.
  • E. laterRailwayCompany
    Indicates that one railway company is the successor or later incarnation of another railway company.
  • 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_69e24551ec7881909a9c924dbea155f6 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f179baa85881909140f41f2428cc98 completed April 29, 2026, 3:23 a.m.
PD Predicate disambiguation batch_69eed2b88d88819096015deb6a648801 completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:24 p.m.