Triple
T21182591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Górno |
E521988
|
entity |
| Predicate | borderedByAdministrativeUnit |
P120977
|
FINISHED |
| Object | Gmina Górno |
—
|
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: Gmina Górno | Statement: [Gmina Górno, borderedByAdministrativeUnit, Gmina Górno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Górno Context triple: [Gmina Górno, borderedByAdministrativeUnit, Gmina Górno]
-
A.
Gmina Górno
chosen
Gmina Górno is a rural administrative district in south-central Poland, located in the Świętokrzyskie Voivodeship.
-
B.
Gmina Góra
Gmina Góra is an administrative district and urban-rural municipality in southwestern Poland, centered on the town of Góra in the Lower Silesian Voivodeship.
-
C.
Gmina Górzyca
Gmina Górzyca is a rural administrative district in western Poland, located in the Lubusz Voivodeship near the German border.
-
D.
Gmina Gorlice
Gmina Gorlice is an administrative district in southern Poland that encompasses the town of Gorlice and surrounding rural areas.
-
E.
Gmina Gnojno
Gmina Gnojno is a rural administrative district in south-central Poland, located within the Świętokrzyskie Voivodeship.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301eb3248190b9f6fc1586651fec |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 3:04 p.m.