Triple
T16116982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gdynia Główna railway station |
E391026
|
entity |
| Predicate | servedBy |
P82
|
FINISHED |
| Object | Polregio |
E400506
|
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: Polregio | Statement: [Gdynia Główna railway station, servedBy, Polregio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Polregio Context triple: [Gdynia Główna railway station, servedBy, Polregio]
-
A.
Polregio
chosen
Polregio is a major Polish regional rail operator providing passenger train services across numerous routes in Poland.
-
B.
Rovigotti
Rovigotti are the inhabitants or natives of the Italian city of Rovigo, located in the Veneto region.
-
C.
Petroupoli
Petroupoli is a suburban municipality in the northwestern part of the Athens metropolitan area in Greece.
-
D.
Codigoro
Codigoro is a municipality in Italy’s Emilia-Romagna region, known for its agricultural landscape and proximity to the Po River delta.
-
E.
Palagano
Palagano is a small municipality in the Emilia-Romagna region of northern Italy, situated in the Apennine mountains within the Province of Modena.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016b5c948190b0f1eccb97ee85cc |
completed | April 17, 2026, 9:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffebab779c8190b466c26f4024aa31 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 5 a.m.