Triple
T16305324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Skała |
E395892
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Gmina Gołcza |
E1113442
|
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 Gołcza | Statement: [Gmina Skała, borderedBy, Gmina Gołcza]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Gołcza Context triple: [Gmina Skała, borderedBy, Gmina Gołcza]
-
A.
Gmina Gołcza
chosen
Gmina Gołcza is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
-
B.
Gmina Gołdap
Gmina Gołdap is an administrative district (gmina) in northeastern Poland, centered on the town of Gołdap near the border with Russia’s Kaliningrad Oblast.
-
C.
Gmina Gorlice
Gmina Gorlice is an administrative district in southern Poland that encompasses the town of Gorlice and surrounding rural areas.
-
D.
Gmina Górzyca
Gmina Górzyca is a rural administrative district in western Poland, located in the Lubusz Voivodeship near the German border.
-
E.
Gmina Głogów
Gmina Głogów is a rural administrative district in southwestern Poland, surrounding the town of Głogów in the Lower Silesian Voivodeship.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288d5619081909d0f8157cc487877 |
completed | April 17, 2026, 7:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001fa3353c8190825b31854a97220c |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:06 a.m.