Triple
T7130207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels-South railway station |
E166166
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | HSL 2 |
E383495
|
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: HSL 2 | Statement: [Brussels-South railway station, railwayLine, HSL 2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HSL 2 Context triple: [Brussels-South railway station, railwayLine, HSL 2]
-
A.
HSL 2
chosen
HSL 2 is a Belgian high-speed railway line primarily used for fast passenger services between major cities and international connections.
-
B.
HSL 3
HSL 3 is a Belgian high-speed railway line that connects Liège to the German border as part of the international high-speed rail corridor between Brussels and Germany.
-
C.
HSL 1
HSL 1 is a Belgian high-speed railway line that forms part of the international route used by Eurostar and other high-speed services between Brussels and neighboring countries.
-
D.
HSL 4
HSL 4 is a Belgian high-speed railway line that connects Antwerp to the Dutch border as part of the international high-speed rail corridor between Brussels and Amsterdam.
-
E.
HSL
HSL is the three-letter National Rail station code for Haslemere railway station in Surrey, England.
- 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.