Triple

T11894668
Position Surface form Disambiguated ID Type / Status
Subject London Passenger Transport Board E283004 entity
Predicate oversawFareSystem P395 FINISHED
Object integrated ticketing and fares for London transport 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: integrated ticketing and fares for London transport | Statement: [London Passenger Transport Board, oversawFareSystem, integrated ticketing and fares for London transport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oversawFareSystem
Context triple: [London Passenger Transport Board, oversawFareSystem, integrated ticketing and fares for London transport]
  • A. fareSystem chosen
    Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
  • B. hasFareControlIntegrationSince
    Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
  • C. operatesTransitSystem
    Indicates that one entity manages and runs the public transportation network or services for another entity or area.
  • D. hasFareZoneSystem
    Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
  • E. fareSystemChange
    Indicates a change in the rules, structure, or method by which fares are calculated, collected, or applied.
  • 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_69d6ab2a90b08190a4e818821cc93e6d completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8dd1172988190a2c13d37220f2f93 completed April 10, 2026, 11:20 a.m.
PD Predicate disambiguation batch_69d8bb2fca4481909893f3428b0871ac completed April 10, 2026, 8:56 a.m.
Created at: April 8, 2026, 9:44 p.m.