Triple
T10638686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasyl |
E250659
|
entity |
| Predicate | hasTransliteration |
P2508
|
FINISHED |
| Object | Vasylʹ |
E250659
|
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: Vasylʹ | Statement: [Vasyl, hasTransliteration, Vasylʹ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vasylʹ Context triple: [Vasyl, hasTransliteration, Vasylʹ]
-
A.
Vasyl
chosen
Vasyl is a common Ukrainian male given name, equivalent to Basil in English.
-
B.
Vadym
Vadym is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
-
C.
Dmytrii
Dmytrii is a masculine given name of Slavic origin, related to the Greek name Demetrius and commonly used in Eastern European cultures.
-
D.
Mykola
Mykola is the Ukrainian form of the given name Nicholas, commonly used in Ukraine and among Ukrainian communities.
-
E.
Bohdan
Bohdan is a masculine given name of Slavic origin, notably borne by the 17th-century Ukrainian Cossack leader Bohdan Khmelnytsky.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfaf12188190a5774d4d64674653 |
completed | April 8, 2026, 11:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d998a4571481908f5010146f7ca5d7 |
completed | April 11, 2026, 12:41 a.m. |
Created at: April 8, 2026, 9:04 p.m.