Triple
T17654268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Jastarnia |
E429579
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Kuźnica |
—
|
NE NERFINISHED |
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: Kuźnica | Statement: [Gmina Jastarnia, hasSettlement, Kuźnica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kuźnica Context triple: [Gmina Jastarnia, hasSettlement, Kuźnica]
-
A.
Kuźnica
chosen
Kuźnica is a small Polish fishing village and seaside resort located on the Hel Peninsula along the Baltic Sea.
-
B.
Kuźnice
Kuźnice is a popular mountain base and trailhead area in Zakopane, Poland, serving as a main starting point for hikes and cable car trips into the Tatra Mountains.
-
C.
Kuźnica-Bruzgi
Kuźnica-Bruzgi is a road border crossing between Poland and Belarus, known as a key transit point in the region and a focal area during the 2021–2022 Belarus–EU border crisis.
-
D.
Kuznica
Kuźnica is a small Polish coastal village and seaside resort located on the Hel Peninsula along the Baltic Sea.
-
E.
Kuźnica Białostocka
Kuźnica Białostocka is a village in northeastern Poland near the Belarusian border, known as a local border crossing point and railway junction.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3fc6e8819080098a3cd0183811 |
completed | April 19, 2026, 5:55 a.m. |
Created at: April 10, 2026, 6:05 a.m.