Triple
T8724727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNCF Voyageurs |
E207101
|
entity |
| Predicate | brand |
P1500
|
FINISHED |
| Object | Eurostar |
E39296
|
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: Eurostar | Statement: [SNCF Voyageurs, brand, Eurostar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eurostar Context triple: [SNCF Voyageurs, brand, Eurostar]
-
A.
Eurostar
chosen
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.
-
B.
Thalys
Thalys is a high-speed international train service connecting major cities in France, Belgium, the Netherlands, and Germany.
-
C.
TGV Lyria
TGV Lyria is a high-speed train service linking France and Switzerland, operated as a joint venture between SNCF and Swiss Federal Railways.
-
D.
TGV
TGV is France’s high-speed intercity train service, renowned for rapid connections between major cities such as Paris and Lille.
-
E.
SNCF Connect
SNCF Connect is the official digital platform and app of the French national railway company, providing online ticket booking, travel planning, and real-time information for trains and other transport services.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d1404948190bc45d14a1ddb1a7e |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfb9fc625c8190bd8fc4e9e456e922 |
completed | April 3, 2026, 1 p.m. |
Created at: March 30, 2026, 6:36 p.m.