Triple

T5707709
Position Surface form Disambiguated ID Type / Status
Subject Chiltern Railways E125825 entity
Predicate owner P347 FINISHED
Object Arriva E119079 NE 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: Arriva | Statement: [Chiltern Railways, owner, Arriva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arriva
Context triple: [Chiltern Railways, owner, Arriva]
  • A. Arriva chosen
    Arriva is a major European public transport company that operates bus, coach, train, tram, and waterbus services across multiple countries.
  • B. Arriva Poland
    Arriva Poland is a Polish public transport operator providing bus and rail services as part of the wider Arriva Group’s European operations.
  • C. Busbridge
    Busbridge is a small village in Surrey, England, situated near the town of Godalming and known for its rural character and historic church.
  • D. Optibús
    Optibús is the bus rapid transit (BRT) system serving the city of León in the Mexican state of Guanajuato.
  • E. Arriva UK Trains
    Arriva UK Trains is a major British train operating company that manages several passenger rail franchises and services across the United Kingdom.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c0082d6fe48190b777fb383769e5c8 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c024892fd88190a91133fc88365410 completed March 22, 2026, 5:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c05a6c17608190a9a808c2c77d937c completed March 22, 2026, 9:09 p.m.
Created at: March 22, 2026, 3:45 p.m.