Triple
T12062684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokółka |
E287212
|
entity |
| Predicate | gmina |
P852
|
FINISHED |
| Object | Gmina Sokółka |
E965554
|
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: Gmina Sokółka | Statement: [Sokółka, gmina, Gmina Sokółka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Sokółka Context triple: [Sokółka, gmina, Gmina Sokółka]
-
A.
Gmina Sokółka
chosen
Gmina Sokółka is an administrative district (gmina) in northeastern Poland that includes the town of Sokółka and surrounding rural areas.
-
B.
Gmina Sękowa
Gmina Sękowa is a rural administrative district in southern Poland, known for its picturesque landscapes and historic wooden churches in the Lesser Poland region.
-
C.
Gmina Skała
Gmina Skała is an administrative district (gmina) in southern Poland, known for encompassing parts of the scenic Ojców area and lying within the Lesser Poland Voivodeship.
-
D.
Gmina Susz
Gmina Susz is an administrative district (gmina) in northern Poland that includes the town of Susz and surrounding rural areas.
-
E.
Gmina Włoszczowa
Gmina Włoszczowa is an administrative district in south-central Poland that includes the town of Włoszczowa and surrounding rural areas.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9043f82248190b05692aa0dc178a8 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a64c8bc8190920c1ed858ea4794 |
completed | May 2, 2026, 2:29 p.m. |
Created at: April 8, 2026, 9:48 p.m.