Triple

T3890307
Position Surface form Disambiguated ID Type / Status
Subject LGV Est européenne E88044 entity
Predicate usedBy P260 FINISHED
Object TGV Lyria E402577 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 Lyria | Statement: [LGV Est européenne, usedBy, TGV Lyria]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TGV Lyria
Context triple: [LGV Est européenne, usedBy, TGV Lyria]
  • A. TGV Lyria chosen
    TGV Lyria is a high-speed train service linking France and Switzerland, operated as a joint venture between SNCF and Swiss Federal Railways.
  • B. TGV Ouigo
    TGV Ouigo is a low-cost high-speed train service operated by SNCF in France, offering budget fares on selected TGV routes.
  • C. Thalys
    Thalys is a high-speed international train service connecting major cities in France, Belgium, the Netherlands, and Germany.
  • D. Eurostar
    Eurostar is a high-speed international train service connecting the United Kingdom with mainland Europe via the Channel Tunnel, linking cities such as London, Paris, and Brussels.
  • E. Bezannes TGV
    Bezannes TGV is a tram terminus and transport hub in the suburb of Bezannes serving the high-speed TGV rail connections near Reims, France.
  • 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_69aed9466d548190939f5217a23ed4ac completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeecb0ba448190aa076865b7762002 completed March 9, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69b56b39f55c819099e5ce90137de570 completed March 14, 2026, 2:05 p.m.
Created at: March 9, 2026, 3:21 p.m.