Triple

T8456897
Position Surface form Disambiguated ID Type / Status
Subject British Rail Class 373 E199940 entity
Predicate usedOnRoute P21808 FINISHED
Object London–Lille E199942 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: London–Lille | Statement: [British Rail Class 373, usedOnRoute, London–Lille]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: London–Lille
Context triple: [British Rail Class 373, usedOnRoute, London–Lille]
  • A. London–Lille chosen
    London–Lille is a high-speed international rail route linking the UK capital with the northern French city of Lille via the Channel Tunnel.
  • B. London–Lyon
    London–Lyon is an international high-speed rail route linking the United Kingdom’s capital with the major city of Lyon in east-central France.
  • C. London–Paris
    London–Paris is a major international rail route connecting the capitals of the United Kingdom and France via the Channel Tunnel.
  • D. London–Brussels
    London–Brussels is a major international high-speed rail route linking the United Kingdom and Belgium via the Channel Tunnel.
  • E. Paris–Lille
    Paris–Lille is a major high-speed rail corridor in northern France connecting the capital Paris with the city of Lille.
  • 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_69ca8318231881908fd1bc1c4d45d286 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe48f180c8190a71cf9d7248ade60 completed March 31, 2026, 3:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce1de232508190803fd2dad21e677f completed April 2, 2026, 7:42 a.m.
Created at: March 30, 2026, 6:10 p.m.