Triple
T19525119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Białystok Voivodeship (Second Polish Republic) |
E488498
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Kolno |
E940693
|
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: Kolno | Statement: [Białystok Voivodeship (Second Polish Republic), containsSettlement, Kolno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kolno Context triple: [Białystok Voivodeship (Second Polish Republic), containsSettlement, Kolno]
-
A.
Kolno
chosen
Kolno is a small town in northeastern Poland known for its traditional character and location within the Podlaskie region.
-
B.
Kolno
Kolno is a small town in northeastern Poland known for its rural character and location within the historic Warmia-Masuria area.
-
C.
Skawina
Skawina is a town in southern Poland near Kraków, known for its industrial facilities and role as a local economic and transport hub.
-
D.
Kolina
Kolina is an Argentine political party aligned with the Peronist movement and associated with the broader Frente de Todos coalition.
-
E.
Chojnik
Chojnik is a village in northern Poland located within the administrative district of Gmina Morąg in the Warmian-Masurian 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63639cfc08190894ac67f7d861a25 |
completed | April 20, 2026, 2:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07472e510881908ffb18bd172c4109 |
completed | May 15, 2026, 4:17 p.m. |
Created at: April 10, 2026, 1:41 p.m.