Triple

T5312934
Position Surface form Disambiguated ID Type / Status
Subject West Coast Route Modernisation E119076 entity
Predicate supportsTrainType P56947 FINISHED
Object tilting trains 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: tilting trains | Statement: [West Coast Route Modernisation, supportsTrainType, tilting trains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsTrainType
Context triple: [West Coast Route Modernisation, supportsTrainType, tilting trains]
  • A. trainTypeUsed chosen
    Indicates that a specific type or category of train is employed or operated in a given context or service.
  • B. usesRollingStockCompatibleWith
    Indicates that one entity operates using rolling stock that is technically and operationally compatible with the rolling stock standards or systems associated with another entity.
  • C. railwayTypeServed
    Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
  • D. supportsMobilityType
    Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
  • E. railServiceType
    Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
  • 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_69bd446b57bc8190a513d2e6c40314f3 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd86f20f008190be7b5848af05f2b8 completed March 20, 2026, 5:42 p.m.
PD Predicate disambiguation batch_69bd84534f9c8190bc19d4812060768d completed March 20, 2026, 5:30 p.m.
Created at: March 20, 2026, 1:54 p.m.