Triple
T14381121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Świdwin County |
E356602
|
entity |
| Predicate | hasRuralGmina |
P46876
|
FINISHED |
| Object | Gmina Rąbino |
E1096132
|
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 Rąbino | Statement: [Świdwin County, hasRuralGmina, Gmina Rąbino]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Rąbino Context triple: [Świdwin County, hasRuralGmina, Gmina Rąbino]
-
A.
Gmina Rąbino
chosen
Gmina Rąbino is a rural administrative district in north-western Poland, situated within the West Pomeranian Voivodeship.
-
B.
Gmina Raba Wyżna
Gmina Raba Wyżna is a rural administrative district in southern Poland, located in Lesser Poland Voivodeship and known for its villages and foothill landscapes.
-
C.
Gmina Rzezawa
Gmina Rzezawa is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
-
D.
Gmina Rytro
Gmina Rytro is a rural administrative district in southern Poland, situated in the Lesser Poland Voivodeship and known for its mountainous landscapes in the Beskid Sądecki range.
-
E.
Gmina Gubin
Gmina Gubin is a rural administrative district in western Poland, situated in Lubusz Voivodeship near the German border.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900bbfb08190a1e56f281a2374c0 |
completed | April 14, 2026, 7:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5511c9e4819089dcbf089ca0dc6a |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 10, 2026, 1:16 a.m.