Triple

T12043481
Position Surface form Disambiguated ID Type / Status
Subject Modane railway station E286723 entity
Predicate hasService P182 FINISHED
Object TGV 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 | Statement: [Modane railway station, hasService, TGV]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TGV
Context triple: [Modane railway station, hasService, TGV]
  • A. TGV chosen
    TGV is France’s high-speed intercity train service, renowned for rapid connections between major cities such as Paris and Lille.
  • B. TGV INOUI
    TGV INOUI is SNCF’s premium high-speed train service in France, offering upgraded comfort, amenities, and service compared to standard TGV trains.
  • C. TGV Est
    TGV Est is a French high-speed train service connecting Paris with eastern France and neighboring European countries such as Germany, Luxembourg, and Switzerland.
  • D. TGV Ouigo
    TGV Ouigo is a low-cost high-speed train service operated by SNCF in France, offering budget fares on selected TGV routes.
  • E. TGV PSE
    TGV PSE is the original generation of French high-speed TGV Sud-Est trainsets that inaugurated high-speed rail service in 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_69d6ab4780948190bdb9f7620c2ac27e completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9040d13108190bd1a969fa62aae5a completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f649dbf081908e76c45e362217c1 completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:47 p.m.