Triple
T11090362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleksandra Khokhlova |
E262234
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Aleksandra |
E260502
|
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: Aleksandra | Statement: [Aleksandra Khokhlova, givenName, Aleksandra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aleksandra Context triple: [Aleksandra Khokhlova, givenName, Aleksandra]
-
A.
Aleksandra
chosen
Aleksandra is a feminine given name of Slavic origin, commonly used in various Eastern and Central European countries.
-
B.
Svetlana
Svetlana is a feminine given name of Slavic origin, most notably borne by Svetlana Alliluyeva, the daughter of Soviet leader Joseph Stalin.
-
C.
Elisaveta
Elisaveta is a feminine given name of Slavic origin, commonly used in Eastern Europe as a variant of Elizabeth.
-
D.
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.
-
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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799e96ca08190838c8a04d1eb2a16 |
completed | April 9, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e496a593c4819090d295119ce50e48 |
completed | April 19, 2026, 8:47 a.m. |
Created at: April 8, 2026, 9:27 p.m.