Triple
T16589757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liszki |
E403052
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Gmina Liszki |
E1223201
|
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 Liszki | Statement: [Liszki, partOf, Gmina Liszki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Liszki Context triple: [Liszki, partOf, Gmina Liszki]
-
A.
Gmina Liszki
chosen
Gmina Liszki is a rural administrative district in southern Poland, located in Kraków County within the Lesser Poland Voivodeship.
-
B.
Gmina Wiślica
Gmina Wiślica is a rural administrative district in south-central Poland, centered on the historic town of Wiślica and located within the Świętokrzyskie Voivodeship.
-
C.
Gmina Lipinki
Gmina Lipinki is a rural administrative district in southern Poland, situated in the Lesser Poland Voivodeship.
-
D.
Gmina Zielonki
Gmina Zielonki is a rural administrative district in southern Poland, located near Kraków in the Lesser Poland Voivodeship.
-
E.
Gmina Wiśniowa
Gmina Wiśniowa is a rural administrative district in southern Poland, located in the Lesser Poland 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599f3d18819082b3e6eef5506731 |
completed | April 18, 2026, 10:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007da6d6f08190a8524b1c955b7c2e |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 5:16 a.m.