Triple
T9397738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | László |
E226387
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Vladislav |
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: Vladislav | Statement: [László, hasVariant, Vladislav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vladislav Context triple: [László, hasVariant, Vladislav]
-
A.
Vladislav
chosen
Vladislav is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
B.
Yaroslav
Yaroslav is a given name of Slavic origin, commonly used in Eastern Europe and associated with several historical rulers and notable figures.
-
C.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
D.
Vladimir
Vladimir is a common Russian male given name of Slavic origin, historically associated with rulers and notably borne by Russian president Vladimir Putin.
-
E.
Vladimir
Vladimir is a historic Russian city east of Moscow, known as one of the medieval capitals of Russia and a key center of the Golden Ring.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51541020819097da2eb60be73760 |
completed | April 1, 2026, 5:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1011aef64819085cbb7e04c2d87b2 |
completed | April 4, 2026, 12:16 p.m. |
Created at: March 30, 2026, 7:46 p.m.