Triple
T20672972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovenian road network |
E508078
|
entity |
| Predicate | mainAxis |
P13659
|
FINISHED |
| Object | Ljubljana–Maribor corridor |
—
|
NE NERFINISHED |
How this triple was built (3 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: Ljubljana–Maribor corridor | Statement: [Slovenian road network, mainAxis, Ljubljana–Maribor corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ljubljana–Maribor corridor Context triple: [Slovenian road network, mainAxis, Ljubljana–Maribor corridor]
-
A.
Koper–Ljubljana road corridor
The Koper–Ljubljana road corridor is a major transport route in southwestern Slovenia that connects the coastal city of Koper with the capital Ljubljana, serving as a key link between the Adriatic coast and the country’s interior.
-
B.
Zagreb–Rijeka corridor
The Zagreb–Rijeka corridor is a major Croatian transport route linking the inland capital region around Zagreb with the Adriatic port city of Rijeka, serving as a key axis for national and international traffic and trade.
-
C.
Zagreb–Split corridor
The Zagreb–Split corridor is a major Croatian transport route linking the capital city Zagreb with the coastal city of Split, serving as a key connection between inland and Adriatic regions.
-
D.
Zagreb–Sisak corridor
The Zagreb–Sisak corridor is a key transportation route in central Croatia that links the capital city of Zagreb with the industrial city of Sisak.
-
E.
Belgrade–Novi Sad corridor
The Belgrade–Novi Sad corridor is a major transport route in Serbia connecting the capital Belgrade with the city of Novi Sad and serving as a key link in regional road and rail networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Ljubljana–Maribor corridor Target entity description: The Ljubljana–Maribor corridor is a key Slovenian transport route linking the capital Ljubljana with the country’s second-largest city, Maribor, and forming part of an important pan-European transit axis.
-
A.
Koper–Ljubljana road corridor
The Koper–Ljubljana road corridor is a major transport route in southwestern Slovenia that connects the coastal city of Koper with the capital Ljubljana, serving as a key link between the Adriatic coast and the country’s interior.
-
B.
Zagreb–Rijeka corridor
The Zagreb–Rijeka corridor is a major Croatian transport route linking the inland capital region around Zagreb with the Adriatic port city of Rijeka, serving as a key axis for national and international traffic and trade.
-
C.
Zagreb–Split corridor
The Zagreb–Split corridor is a major Croatian transport route linking the capital city Zagreb with the coastal city of Split, serving as a key connection between inland and Adriatic regions.
-
D.
Zagreb–Sisak corridor
The Zagreb–Sisak corridor is a key transportation route in central Croatia that links the capital city of Zagreb with the industrial city of Sisak.
-
E.
Belgrade–Novi Sad corridor
The Belgrade–Novi Sad corridor is a major transport route in Serbia connecting the capital Belgrade with the city of Novi Sad and serving as a key link in regional road and rail networks.
- F. None of above. chosen
Provenance (2 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5cb1fc88190805f623e93a70368 |
completed | April 20, 2026, 11:24 p.m. |
Created at: April 16, 2026, 11:44 a.m.