Triple
T6359109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Słowiński National Park |
E143064
|
entity |
| Predicate | nearestTown |
P350
|
FINISHED |
| Object | Łeba |
E294188
|
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: Łeba | Statement: [Słowiński National Park, nearestTown, Łeba]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Łeba Context triple: [Słowiński National Park, nearestTown, Łeba]
-
A.
Łeba
chosen
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
B.
Wołosate
Wołosate is a small village in southeastern Poland’s Bieszczady Mountains, known as a remote hiking base and the terminus of the Main Beskid Trail.
-
C.
Mrągowo
Mrągowo is a picturesque town in northeastern Poland known for its lakeside setting and popular summer cultural and music festivals.
-
D.
Piła
Piła is a city in northwestern Poland known as a regional economic and transport center in the Greater Poland Voivodeship.
-
E.
Tczew
Tczew is a historic town in northern Poland on the Vistula River, known for its important railway bridges and role as a regional transport hub.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f72f8481908f9df0c0cdf22a52 |
completed | March 22, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d190aa70f0819088998b0e895ea36a |
completed | April 4, 2026, 10:28 p.m. |
Created at: March 22, 2026, 4:32 p.m.