Triple
T315937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutaisi |
E7705
|
entity |
| Predicate | hasSisterCity |
P919
|
FINISHED |
| Object | Białystok |
E28010
|
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: Białystok | Statement: [Kutaisi, hasSisterCity, Białystok]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Białystok Context triple: [Kutaisi, hasSisterCity, Białystok]
-
A.
Białystok
chosen
Białystok is a city in northeastern Poland best known as the birthplace of L. L. Zamenhof and the cradle of the international language Esperanto.
-
B.
Łódź
Łódź is one of Poland’s largest cities, historically known as a major industrial and textile manufacturing center.
-
C.
Gdańsk
Gdańsk is a major Polish port city on the Baltic Sea, known for its rich Hanseatic history, shipyards, and role in the origins of the Solidarity movement.
-
D.
Wilno
Wilno is the historical Polish name for Vilnius, a major cultural and political center of the region that served as an important city in the interwar Second Polish Republic.
-
E.
Gdynia
Gdynia is a major seaport city on Poland’s Baltic coast, developed rapidly in the 20th century into one of the country’s key maritime and economic centers.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea6462148190825acc57f6d2adaf |
completed | Feb. 28, 2026, 1:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3c8b8d7d88190b43f7b6b0289445f |
completed | March 1, 2026, 5:03 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.