Triple
T21383531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Białogard |
E527426
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Karlino |
—
|
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: Karlino | Statement: [Białogard, hasTwinTown, Karlino]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karlino Context triple: [Białogard, hasTwinTown, Karlino]
-
A.
Karlino
chosen
Karlino is a small town in northwestern Poland known for its location in the historical region of Pomerania.
-
B.
Kalinin
Kalinin is the former Soviet-era name of the Russian city now known as Tver, reflecting its renaming in honor of Bolshevik leader Mikhail Kalinin.
-
C.
Yuriev
Yuriev is the historical name of the Ukrainian city now known as Bila Tserkva, an important regional center south of Kyiv.
-
D.
Kirovo
Kirovo was the Soviet-era name for the Ukrainian city now known as Kropyvnytskyi, reflecting its renaming in honor of Bolshevik leader Sergei Kirov.
-
E.
Kirovakan
Kirovakan is the former name of Vanadzor, a major industrial city in northern Armenia.
- 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_69e0b51f363c8190944000ab5523b02b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0f05278819096c511035ffc9777 |
completed | April 22, 2026, 11:28 a.m. |
Created at: April 16, 2026, 5:12 p.m.