Triple
T5129665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladyslav Kryklii |
E115664
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vladyslav |
E331996
|
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: Vladyslav | Statement: [Vladyslav Kryklii, givenName, Vladyslav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vladyslav Context triple: [Vladyslav Kryklii, givenName, Vladyslav]
-
A.
Vladislav
chosen
Vladislav is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
B.
Vasyl
Vasyl is a common Ukrainian male given name, equivalent to Basil in English.
-
C.
Vadym
Vadym is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
-
D.
Sviatoslav
Sviatoslav is a masculine given name of Slavic origin, historically borne by medieval rulers such as Sviatoslav I of Kiev.
-
E.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7827c764819086da3b79f2020224 |
completed | March 20, 2026, 4:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bef7f117ac8190a03379437484627b |
completed | March 21, 2026, 7:56 p.m. |
Created at: March 20, 2026, 1:42 p.m.