Triple
T22243299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Łączna |
E549776
|
entity |
| Predicate | hasAdministrativeCentre |
P1474
|
FINISHED |
| Object | Łączna |
—
|
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: Łączna | Statement: [Gmina Łączna, hasAdministrativeCentre, Łączna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Łączna Context triple: [Gmina Łączna, hasAdministrativeCentre, Łączna]
-
A.
Łączna
chosen
Łączna is a village in south-central Poland that forms part of the local administrative area governed from the nearby town of Suchedniów.
-
B.
Łączno
Łączno is a village in northern Poland located within the administrative district of Gmina Morąg in the Warmian-Masurian Voivodeship.
-
C.
Zalezianka
Zalezianka is a small village in south-central Poland, located within the administrative district of Gmina Łączna in the Świętokrzyskie Voivodeship.
-
D.
Równe
Równe is a town in western Poland that serves as a twin town to Głogów.
-
E.
Sylko
Sylko is a brand of sewing and embroidery threads historically associated with the textile company J. & P. Coats.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1321655b0819091f1ddf06c67f3c2 |
completed | April 28, 2026, 10:17 p.m. |
Created at: April 16, 2026, 8:38 p.m.