Triple
T19855932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volodymyr Kistion |
E477131
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Volodymyr |
—
|
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: Volodymyr | Statement: [Volodymyr Kistion, givenName, Volodymyr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Volodymyr Context triple: [Volodymyr Kistion, givenName, Volodymyr]
-
A.
Volodymyr
chosen
Volodymyr is a historic city in western Ukraine known for its medieval heritage and role as a former center of the Volhynia region.
-
B.
Volodymyr Sviatoslavych
Volodymyr Sviatoslavych was a grand prince of Kyivan Rus’ best known for Christianizing the realm at the end of the 10th century.
-
C.
Mykhailo
Mykhailo is a masculine given name of Slavic origin, commonly used in Ukrainian and other Eastern European cultures as a form of Michael.
-
D.
Oleksiy
Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
-
E.
Ihor
Ihor is a Ukrainian given name, commonly considered the Ukrainian form of Igor.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6586c14fc81908d34785f1088b0a9 |
completed | April 20, 2026, 4:46 p.m. |
Created at: April 10, 2026, 1:51 p.m.