Triple
T16699541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proskuriv |
E405807
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Проскурів |
E935102
|
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: Проскурів | Statement: [Proskuriv, hasAlternativeName, Проскурів]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Проскурів Context triple: [Proskuriv, hasAlternativeName, Проскурів]
-
A.
Proskurov
chosen
Proskurov is the former name of the Ukrainian city now known as Khmelnytskyi, a regional center in western Ukraine.
-
B.
Krasyliv
Krasyliv is a small town in western Ukraine known for its agricultural surroundings and local light industry within Khmelnytskyi Oblast.
-
C.
Snihurivka
Snihurivka is a small town in southern Ukraine known for its agricultural surroundings and strategic location in Mykolaiv Oblast.
-
D.
Pryluky
Pryluky is a historic city in northern Ukraine known for its Cossack heritage and role as a regional cultural and economic center.
-
E.
Letychiv
Letychiv is an urban-type settlement in western Ukraine known for its historic fortress and role as a local administrative center.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e383300d108190911e3cba8e07f2dd |
completed | April 18, 2026, 1:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009d38a1348190bf51af9847a16aa5 |
completed | May 10, 2026, 2:59 p.m. |
Created at: April 10, 2026, 5:19 a.m.