Triple
T5353161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Gothenburg |
E102624
|
entity |
| Predicate | hasRailShuttleConnectionsTo |
P3493
|
FINISHED |
| Object | inland terminals in Sweden |
—
|
LITERAL 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: inland terminals in Sweden | Statement: [Port of Gothenburg, hasRailShuttleConnectionsTo, inland terminals in Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailShuttleConnectionsTo Context triple: [Port of Gothenburg, hasRailShuttleConnectionsTo, inland terminals in Sweden]
-
A.
hasShuttleLine
chosen
Indicates that there is a shuttle service or route operating between the related entities.
-
B.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
E.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
- F. None of above.
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_69bd43d8f7248190b64c140734b5c9a8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd861327288190b3f2720ce81e0de6 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.