Triple
T14381287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eindhoven Strijp-S railway station |
E356607
|
entity |
| Predicate | hasStationCode |
P1289
|
FINISHED |
| Object | Esv |
E352786
|
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: Esv | Statement: [Eindhoven Strijp-S railway station, hasStationCode, Esv]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Esv Context triple: [Eindhoven Strijp-S railway station, hasStationCode, Esv]
-
A.
Esv
chosen
Esv is the official Dutch railway station code used to identify Eindhoven Strijp-S station in the Netherlands.
-
B.
Ehv
Ehv is the official station code used to identify Eindhoven Centraal railway station in the Netherlands.
-
C.
ES-VI
ES-VI is the ISO 3166-2 subdivision code that uniquely identifies the Spanish province of Álava within Spain’s administrative coding system.
-
D.
ESVK
ESVK is a German ice hockey club based in Kaufbeuren, Bavaria, competing in the national league system.
-
E.
ESSV
ESSV is the ICAO airport code for Visby Airport, the main airport serving the island of Gotland in Sweden.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900bbfb08190a1e56f281a2374c0 |
completed | April 14, 2026, 7:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c590660819090652e75418f2747 |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:16 a.m.