Triple
T22834649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Gnojno |
E565909
|
entity |
| Predicate | seat |
P75
|
FINISHED |
| Object | Gnojno |
—
|
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: Gnojno | Statement: [Gmina Gnojno, seat, Gnojno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gnojno Context triple: [Gmina Gnojno, seat, Gnojno]
-
A.
Gnojno
chosen
Gnojno is a village in south-central Poland located within the administrative area of Busko County in the Świętokrzyskie Voivodeship.
-
B.
Glodzhevo
Glodzhevo is a small town in northeastern Bulgaria, situated within Ruse Province near the Romanian border.
-
C.
Dobro Pole
Dobro Pole is a mountainous area on the Macedonian–Greek border best known as the site of a decisive World War I battle that helped break the Balkan front.
-
D.
Zgorzelec
Zgorzelec is a town in southwestern Poland on the Lusatian Neisse River, forming a twin city with Görlitz in Germany and serving as an important local cultural and transport hub.
-
E.
Gonjače
Gonjače is a small village in western Slovenia known for its scenic hilltop location and panoramic tower overlooking the Brda wine-growing region.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2e3e7481909d12dc5008136880 |
completed | April 29, 2026, 3:42 a.m. |
Created at: April 17, 2026, 3:35 p.m.