Triple
T7130233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels-South railway station |
E166166
|
entity |
| Predicate | servesRoute |
P31354
|
FINISHED |
| Object | Brussels–Paris |
E199652
|
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: Brussels–Paris | Statement: [Brussels-South railway station, servesRoute, Brussels–Paris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brussels–Paris Context triple: [Brussels-South railway station, servesRoute, Brussels–Paris]
-
A.
Paris–Brussels
chosen
Paris–Brussels is a major international high-speed rail corridor linking the capitals of France and Belgium.
-
B.
Brussels–Cologne
Brussels–Cologne is a major international high-speed rail corridor linking Belgium’s capital with the German city of Cologne.
-
C.
Brussels–Amsterdam
Brussels–Amsterdam is a major international high-speed rail route connecting the capitals of Belgium and the Netherlands.
-
D.
Frankfurt–Brussels
Frankfurt–Brussels is a major international high-speed rail route linking Germany and Belgium, commonly served by InterCityExpress (ICE) trains.
-
E.
Paris–Amsterdam
Paris–Amsterdam is a major international high-speed rail route linking the capitals of France and the Netherlands.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e66dc2388190bdec018f1cc6b20a |
completed | March 27, 2026, 8:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7ad8d00848190a5a4b9b64b3426e7 |
completed | March 28, 2026, 10:29 a.m. |
Created at: March 27, 2026, 2:44 p.m.