Triple

T38604971
Position Surface form Disambiguated ID Type / Status
Subject Serco-Abellio joint venture E934316 entity
Predicate railFranchiseOperated P121930 FINISHED
Object Northern Rail NE NERFINISHED

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: Northern Rail | Statement: [Serco-Abellio joint venture, railFranchiseOperated, Northern Rail]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railFranchiseOperated
Context triple: [Serco-Abellio joint venture, railFranchiseOperated, Northern Rail]
  • A. railFranchise
    Indicates a contractual relationship in which a company is granted the right to operate rail services or manage rail infrastructure within a specified area or route.
  • B. operatesRailNetworkOf
    Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
  • C. railFranchiseAwardedBy
    Indicates that a rail franchise is granted or assigned to an operator by a specific awarding authority or organization.
  • D. hasRailTransportOperator chosen
    Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
  • E. operatedOnRailroad
    Indicates that an entity conducted operations or provided services on a railroad system.
  • 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_69f76ecc17688190b389b693a5927501 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcdb0de8c08190928cd1323f80ab5c completed May 7, 2026, 6:33 p.m.
PD Predicate disambiguation batch_69fcd9017dd88190b32a73fe78909740 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:32 p.m.