Triple
T13605161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gare de Besançon-Viotte |
E325041
|
entity |
| Predicate | serviceType |
P87
|
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: [Gare de Besançon-Viotte, serviceType, TGV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TGV Context triple: [Gare de Besançon-Viotte, serviceType, 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07e442c819086a8cbb967c03ad3 |
completed | April 12, 2026, 2:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f93ec588190993baec788d22670 |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:50 p.m.