Triple
T16558443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kocmyrzów-Luborzyca |
E402270
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Zielonki |
E402272
|
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: Zielonki | Statement: [Kocmyrzów-Luborzyca, borders, Zielonki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zielonki Context triple: [Kocmyrzów-Luborzyca, borders, Zielonki]
-
A.
Zielonki
Zielonki is a village in southern Poland located within the administrative district of Gmina Trzyciąż.
-
B.
Zielonki
chosen
Zielonki is a village in southern Poland that functions as a suburban community just north of Kraków, blending residential areas with local services and small-scale agriculture.
-
C.
Dzierzążnia
Dzierzążnia is a village in east-central Poland that serves as a local rural settlement within Płońsk County in the Masovian Voivodeship.
-
D.
Ryglice
Ryglice is a small town in southern Poland known for its rural character and location in the historical region of Lesser Poland.
-
E.
Jasień
Jasień is a prominent mountain peak in southern Poland that forms part of the Beskid Wyspowy range in the Western Carpathians.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576bce0c819087ab36f7dec5c394 |
completed | April 18, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067bcb698819092ede6ba4f8a4a2b |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:15 a.m.