Triple
T18999319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vendôme-Villiers-sur-Loir TGV |
E464902
|
entity |
| Predicate | hasService |
P182
|
FINISHED |
| Object | TGV Inoui |
—
|
NE NERFINISHED |
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 Inoui | Statement: [Vendôme-Villiers-sur-Loir TGV, hasService, TGV Inoui]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TGV Inoui Context triple: [Vendôme-Villiers-sur-Loir TGV, hasService, TGV Inoui]
-
A.
TGV INOUI
chosen
TGV INOUI is SNCF’s premium high-speed train service in France, offering upgraded comfort, amenities, and service compared to standard TGV trains.
-
B.
TGV PSE
TGV PSE is the original generation of French high-speed TGV Sud-Est trainsets that inaugurated high-speed rail service in France.
-
C.
TGV Ouigo
TGV Ouigo is a low-cost high-speed train service operated by SNCF in France, offering budget fares on selected TGV routes.
-
D.
TGV
TGV is France’s high-speed intercity train service, renowned for rapid connections between major cities such as Paris and Lille.
-
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 (2 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d684d37c8190b975f04a47fa7b92 |
completed | April 20, 2026, 7:32 a.m. |
Created at: April 10, 2026, 12:01 p.m.