Triple
T11745828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilia |
E279277
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Liliya |
E615016
|
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: Liliya | Statement: [Lilia, hasVariant, Liliya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Liliya Context triple: [Lilia, hasVariant, Liliya]
-
A.
Ludmila
Ludmila is the heroine of Alexander Pushkin’s narrative poem "Ruslan and Ludmila," known as a beautiful Kievan princess whose abduction sets the story’s adventurous plot in motion.
-
B.
Lyudmila
Lyudmila is a Russian linguist and the former First Lady of Russia, known for being the ex-wife of President Vladimir Putin.
-
C.
Lyudmila
chosen
Lyudmila is a common Russian female given name, notably borne by figures such as Soviet World War II sniper Lyudmila Pavlichenko.
-
D.
Zhanna
Zhanna is a feminine given name commonly used in Russian and other Slavic cultures, equivalent to Jeanne or Joanna.
-
E.
Yulia
Yulia is a feminine given name, commonly used in Slavic countries as a form of the name Julia.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f2a38c8190a682d8dae1ab9415 |
completed | April 10, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f019f5f29c81909d80a9e6127ec6ef |
completed | April 28, 2026, 2:22 a.m. |
Created at: April 8, 2026, 9:41 p.m.