Triple
T18778868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubin County |
E459200
|
entity |
| Predicate | hasRuralGmina |
P46876
|
FINISHED |
| Object | Gmina Rudna |
—
|
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 Rudna | Statement: [Lubin County, hasRuralGmina, Gmina Rudna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Rudna Context triple: [Lubin County, hasRuralGmina, Gmina Rudna]
-
A.
Gmina Rudna
chosen
Gmina Rudna is a rural administrative district in southwestern Poland, located in the Lower Silesian Voivodeship.
-
B.
Gmina Ruda Maleniecka
Gmina Ruda Maleniecka is a rural administrative district in south-central Poland, situated within the Świętokrzyskie Voivodeship.
-
C.
Gmina Radecznica
Gmina Radecznica is a rural administrative district in eastern Poland, located within the Lublin Voivodeship.
-
D.
Gmina Grudusk
Gmina Grudusk is a rural administrative district in east-central Poland, situated in Ciechanów County within the Masovian Voivodeship.
-
E.
Gmina Radwanice
Gmina Radwanice is a rural administrative district in southwestern Poland, known for its agricultural character and small villages within the Lower Silesian 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933d2d048190a42480edc70bf086 |
completed | April 20, 2026, 2:45 a.m. |
Created at: April 10, 2026, 11:52 a.m.