Triple
T8633924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intercity Brussels |
E204472
|
entity |
| Predicate | operator |
P179
|
FINISHED |
| Object | SNCB |
E78978
|
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: SNCB | Statement: [Intercity Brussels, operator, SNCB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SNCB Context triple: [Intercity Brussels, operator, SNCB]
-
A.
SNCB/NMBS
chosen
SNCB/NMBS is the Belgian national railway company responsible for operating most passenger train services and managing much of the rail infrastructure in Belgium.
-
B.
Infrabel
Infrabel is the Belgian railway infrastructure manager responsible for the construction, maintenance, and operation of the national rail network.
-
C.
Intercity Brussels
Intercity Brussels is an international high-speed train service connecting the Netherlands with Brussels in Belgium.
-
D.
ProRail
ProRail is the Dutch government-owned company responsible for managing and maintaining the national railway infrastructure in the Netherlands.
-
E.
STIB-MIVB
STIB-MIVB is the primary public transport company in Brussels, Belgium, operating the city’s metro, tram, and bus networks.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4743d31881908cf9fc3838c4bdd9 |
completed | March 31, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebc13073c8190ad6e92b8f7161739 |
completed | April 2, 2026, 6:57 p.m. |
Created at: March 30, 2026, 6:27 p.m.