Triple

T27550984
Position Surface form Disambiguated ID Type / Status
Subject Old Oak Common E695497 entity
Predicate futureTransportRole P6821 FINISHED
Object major London rail interchange 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: major London rail interchange | Statement: [Old Oak Common, futureTransportRole, major London rail interchange]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: futureTransportRole
Context triple: [Old Oak Common, futureTransportRole, major London rail interchange]
  • A. transportRole
    Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
  • B. transportationRole chosen
    Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
  • C. mobilityRole
    Indicates the functional role or capacity an entity has in enabling, supporting, or performing movement or transportation.
  • D. futureRollingStock
    Indicates that an entity is designated to serve as rolling stock (e.g., trains or rail vehicles) at some point in the future, rather than in the present or past.
  • E. formerTransport
    Indicates that an entity previously served as a means of transportation for another entity but no longer does so.
  • 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_69ef5386c3e08190bfe33aa326e1f72b completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62f8b88c88190a327896be2af2f06 completed May 2, 2026, 5:08 p.m.
PD Predicate disambiguation batch_69f62c1921008190a62675a31f66a875 completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 1:34 p.m.