Triple

T8456901
Position Surface form Disambiguated ID Type / Status
Subject British Rail Class 373 E199940 entity
Predicate family P566 FINISHED
Object TGV family E445505 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: TGV family | Statement: [British Rail Class 373, family, TGV family]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TGV family
Context triple: [British Rail Class 373, family, TGV family]
  • A. TGV PSE
    TGV PSE is the original generation of French high-speed TGV Sud-Est trainsets that inaugurated high-speed rail service in France.
  • B. TGV Duplex trainset
    The TGV Duplex trainset is a high-speed, double-decker French train designed to carry large numbers of passengers efficiently on long-distance routes.
  • C. TGV Réseau
    TGV Réseau is a later-generation French high-speed trainset used by SNCF, designed for improved performance and comfort on the expanding TGV network.
  • D. TGV chosen
    TGV is France’s high-speed intercity train service, renowned for rapid connections between major cities such as Paris and Lille.
  • E. TGV Ouigo
    TGV Ouigo is a low-cost high-speed train service operated by SNCF in France, offering budget fares on selected TGV routes.
  • 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_69ce39caf4bc8190a1850b2124684a2a completed April 2, 2026, 9:41 a.m.
Created at: March 30, 2026, 6:10 p.m.