Triple
T12166528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gare du Midi – Zuidstation |
E289845
|
entity |
| Predicate | railwayStationCode |
P1289
|
FINISHED |
| Object | BRU |
E192169
|
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: BRU | Statement: [Gare du Midi – Zuidstation, railwayStationCode, BRU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BRU Context triple: [Gare du Midi – Zuidstation, railwayStationCode, BRU]
-
A.
BRU
chosen
BRU is the IATA airport code for Brussels Airport, the main international airport serving Brussels, Belgium.
-
B.
Brun
Brun is a given name and surname of Germanic origin, closely related to and often used as a variant of Bruno.
-
C.
Buurse
Buurse is a small village in the eastern Netherlands, near the German border, known for its rural landscape and nature reserves.
-
D.
Brugg
Brugg is a historic Swiss town in the canton of Aargau, known for its medieval heritage and strategic location near the confluence of the Aare, Reuss, and Limmat rivers.
-
E.
Brum
Brum is a colloquial nickname commonly used to refer to the city of Birmingham in England and its local culture.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f6a2716081909620a9d11cfcc2d8 |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:50 p.m.