Triple

T25179243
Position Surface form Disambiguated ID Type / Status
Subject Bedford to St Pancras services E630536 entity
Predicate operatedOnInfrastructureManagedBy P168522 FINISHED
Object Network 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: Network Rail | Statement: [Bedford to St Pancras services, operatedOnInfrastructureManagedBy, Network Rail]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatedOnInfrastructureManagedBy
Context triple: [Bedford to St Pancras services, operatedOnInfrastructureManagedBy, Network Rail]
  • A. infrastructureManagedBy chosen
    Indicates that the responsibility for operating, maintaining, or overseeing a piece of infrastructure lies with a specified managing entity.
  • B. ownerOfInfrastructureUsed
    Indicates that one entity owns the infrastructure that is being used by another entity or activity.
  • C. ownedInfrastructureClass
    Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
  • D. operatedByOrganization
    Indicates that an activity, facility, or system is run, managed, or controlled by a specific organization.
  • E. oftenOperatedBy
    Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
  • 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_69e75a88fdf081908e47ae6e195c14e1 completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f6c1265c208190aacd2b551f8f0f82 completed May 3, 2026, 3:29 a.m.
PD Predicate disambiguation batch_69f6bd2415fc81908c23c311aebce66f completed May 3, 2026, 3:12 a.m.
Created at: April 21, 2026, 12:35 p.m.