Triple
T13084004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noteć |
E310281
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Nakło nad Notecią |
E667196
|
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: Nakło nad Notecią | Statement: [Noteć, passesNear, Nakło nad Notecią]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nakło nad Notecią Context triple: [Noteć, passesNear, Nakło nad Notecią]
-
A.
Nakło nad Notecią
chosen
Nakło nad Notecią is a historic town in north-central Poland, situated on the Noteć River and serving as an important local center of the Krajna region.
-
B.
Łęczna
Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
-
C.
Muszyna
Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
-
D.
Ciechocinek
Ciechocinek is a Polish spa town renowned for its historic saline graduation towers and therapeutic health resorts.
-
E.
Niepołomice
Niepołomice is a historic town in southern Poland known for its royal castle, proximity to the Niepołomice Forest, and location near Kraków.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d60e7b48819087e4583a5736c1df |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 9:02 p.m.