Triple
T15947241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kozłowo |
E386715
|
entity |
| Predicate | isSeatOf |
P62
|
FINISHED |
| Object | Gmina Kozłowo |
E1184310
|
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 Kozłowo | Statement: [Kozłowo, isSeatOf, Gmina Kozłowo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gmina Kozłowo Context triple: [Kozłowo, isSeatOf, Gmina Kozłowo]
-
A.
Gmina Kozłowo
chosen
Gmina Kozłowo is a rural administrative district in northern Poland, encompassing the village of Kozłowo and surrounding settlements.
-
B.
Gmina Kozłów
Gmina Kozłów is a rural administrative district in southern Poland, located within Lesser Poland Voivodeship.
-
C.
Gmina Kościelisko
Gmina Kościelisko is a rural administrative district in southern Poland, situated in the Tatra Mountains near Zakopane and known for its scenic landscapes and traditional highlander culture.
-
D.
Gmina Końskie
Gmina Końskie is an administrative district in south-central Poland that includes the town of Końskie and surrounding rural areas within Końskie County.
-
E.
Gmina Włoszczowa
Gmina Włoszczowa is an administrative district in south-central Poland that includes the town of Włoszczowa and surrounding rural areas.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156d2fda8819085279d2a0f8a02ab |
completed | April 16, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffbe76df6481909f8246099faa377a |
completed | May 9, 2026, 11:08 p.m. |
Created at: April 10, 2026, 4:53 a.m.