Triple
T2874031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimir |
E56831
|
entity |
| Predicate | hasFeminineForm |
P1613
|
FINISHED |
| Object |
Vladimira
Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
|
E307334
|
NE FINISHED |
How this triple was built (4 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: Vladimira | Statement: [Vladimir, hasFeminineForm, Vladimira]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vladimira Context triple: [Vladimir, hasFeminineForm, Vladimira]
-
A.
Lopokova
Lopokova is the surname of Lydia Lopokova, a renowned Russian ballerina associated with the Ballets Russes and later known for her marriage to economist John Maynard Keynes.
-
B.
Romeyka
Romeyka is an endangered Greek dialect spoken mainly in northeastern Turkey, notable for preserving many archaic features of Ancient Greek.
-
C.
Zhdanova
Zhdanova is a Russian-language surname commonly borne by women and associated with several notable figures in Russian and post-Soviet public life.
-
D.
Aleksandra
Aleksandra is a feminine given name of Slavic origin, commonly used in various Eastern and Central European countries.
-
E.
Ivanova
Ivanova is a common Slavic surname, particularly prevalent in Russia and other Eastern European countries, typically indicating female lineage from someone named Ivan.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Vladimira Triple: [Vladimir, hasFeminineForm, Vladimira]
Generated description
Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Vladimira Target entity description: Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
-
A.
Lopokova
Lopokova is the surname of Lydia Lopokova, a renowned Russian ballerina associated with the Ballets Russes and later known for her marriage to economist John Maynard Keynes.
-
B.
Romeyka
Romeyka is an endangered Greek dialect spoken mainly in northeastern Turkey, notable for preserving many archaic features of Ancient Greek.
-
C.
Zhdanova
Zhdanova is a Russian-language surname commonly borne by women and associated with several notable figures in Russian and post-Soviet public life.
-
D.
Aleksandra
Aleksandra is a feminine given name of Slavic origin, commonly used in various Eastern and Central European countries.
-
E.
Ivanova
Ivanova is a common Slavic surname, particularly prevalent in Russia and other Eastern European countries, typically indicating female lineage from someone named Ivan.
- F. None of above. chosen
Provenance (5 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe0032ddc8190bb4d15ec7e3c63e8 |
completed | March 7, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b03153b5048190925bfacc07f2db66 |
completed | March 10, 2026, 2:57 p.m. |
| NEDg | Description generation | batch_69b031d1f4d88190a9a77db5a6b02d89 |
completed | March 10, 2026, 2:59 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b034eded648190a6b1d00aaa2a61f2 |
completed | March 10, 2026, 3:12 p.m. |
Created at: March 6, 2026, 10:03 p.m.