Triple
T22857737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenkiv Uyezd |
E566829
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Zenkiv |
—
|
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: Zenkiv | Statement: [Zenkiv Uyezd, capital, Zenkiv]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zenkiv Context triple: [Zenkiv Uyezd, capital, Zenkiv]
-
A.
Zenkiv
chosen
Zenkiv is a historic town in central Ukraine, known for its role as a local administrative and cultural center in the Poltava region.
-
B.
Vasylkiv
Vasylkiv is a historic town in central Ukraine, known for its long-standing administrative role and its location near the capital city of Kyiv.
-
C.
Letychiv
Letychiv is an urban-type settlement in western Ukraine known for its historic fortress and role as a local administrative center.
-
D.
Zinkiv
Zinkiv is a small historic town in central Ukraine known for its traditional architecture and role as a local administrative and cultural center.
-
E.
Hirnyky
Hirnyky is the Ukrainian nickname meaning "Miners," commonly used to refer to the football club FC Shakhtar Donetsk and its players.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ebe3f9c8190a864f4e84dc7795d |
completed | April 29, 2026, 3:45 a.m. |
Created at: April 17, 2026, 3:37 p.m.