Triple
T9190559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wydminy |
E220576
|
entity |
| Predicate | isSeatOf |
P62
|
FINISHED |
| Object | Gmina Wydminy |
E783914
|
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 Wydminy | Statement: [Wydminy, isSeatOf, Gmina Wydminy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Wydminy Context triple: [Wydminy, isSeatOf, Gmina Wydminy]
-
A.
Gmina Wydminy
chosen
Gmina Wydminy is a rural administrative district in northeastern Poland’s Warmian-Masurian Voivodeship, known for its lakes and forests in the Masurian region.
-
B.
Gmina Drwinia
Gmina Drwinia is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
-
C.
Gmina Nawojowa
Gmina Nawojowa is a rural administrative district in southern Poland, located in Nowy Sącz County within the Lesser Poland Voivodeship.
-
D.
Gmina Gubin
Gmina Gubin is a rural administrative district in western Poland, situated in Lubusz Voivodeship near the German border.
-
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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5bf25c081909e651b67ef8ecc33 |
completed | April 1, 2026, 8:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d065d5e81c8190b6687999a87fd559 |
completed | April 4, 2026, 1:13 a.m. |
Created at: March 30, 2026, 7:24 p.m.