Triple
T12143153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ustka |
E289241
|
entity |
| Predicate | hasRailConnectionTo |
P848
|
FINISHED |
| Object | Słupsk |
E178809
|
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: Słupsk | Statement: [Ustka, hasRailConnectionTo, Słupsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Słupsk Context triple: [Ustka, hasRailConnectionTo, Słupsk]
-
A.
Słupsk
chosen
Słupsk is a historic city in northern Poland known for its medieval architecture and location near the Baltic Sea.
-
B.
Koszalin
Koszalin is a city in northwestern Poland near the Baltic Sea, known as a regional cultural and economic center.
-
C.
Świdwin
Świdwin is a historic town in northwestern Poland, known for its medieval castle and location in the West Pomeranian Voivodeship.
-
D.
Świnoujście
Świnoujście is a Polish port city and seaside resort on the Baltic Sea, known for its wide beaches, spa facilities, and strategic location at the mouth of the Świna River.
-
E.
Giżycko
Giżycko is a popular lakeside town in northeastern Poland, known as a major sailing and tourism center in the Masurian Lake District.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915aacaa08190b31f54e230334406 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda8fd6f5081908de9a9e3df28a8ea |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 8, 2026, 9:49 p.m.