Triple

T30275035
Position Surface form Disambiguated ID Type / Status
Subject MTC E769913 entity
Predicate usedByTransportAuthority P7691 FINISHED
Object Transport for London 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: Transport for London | Statement: [MTC, usedByTransportAuthority, Transport for London]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedByTransportAuthority
Context triple: [MTC, usedByTransportAuthority, Transport for London]
  • A. usedByTransitSystem
    Indicates that something is utilized or operated by a transit or public transportation system.
  • B. hasTransportAuthority chosen
    Indicates that one entity holds official power or responsibility to manage, regulate, or oversee transportation services or infrastructure for another entity or area.
  • C. usesTransportNetwork
    Indicates that an entity makes use of a transport network (such as roads, rail, or transit systems) to move people, goods, or services.
  • D. publicTransportAllowed
    Indicates that the use of public transportation is permitted or authorized in the given context or for the specified entities.
  • E. servedByTransportation
    Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
  • 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_69f224868fa8819099127eaf8855a28f completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f7805ce6208190ac6dbd9c97989978 completed May 3, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f77956ec648190ba4fb7e9d83fd107 completed May 3, 2026, 4:35 p.m.
Created at: April 29, 2026, 7:44 p.m.