Triple
T1671176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olga Khokhlova |
E36128
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Olga |
E136344
|
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: Olga | Statement: [Olga Khokhlova, givenName, Olga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Olga Context triple: [Olga Khokhlova, givenName, Olga]
-
A.
Olga
chosen
Olga is a female given name of Russian origin, historically borne by several notable figures including Russian grand duchesses and saints.
-
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.
Olga Loyev
Olga Loyev was the wife of the famed Yiddish writer Sholem Aleichem and a supportive partner throughout his literary career.
-
D.
Aloysya
Aloysya is a given name, typically a feminine variant of Aloysius, used in various cultures and languages.
-
E.
Tatyana
Tatyana is a feminine given name of Slavic origin, particularly common in Russian-speaking countries.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62439e48819084e46b2719cdac58 |
completed | March 6, 2026, 5:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adbf44b62081908322c41ef1518297 |
completed | March 8, 2026, 6:26 p.m. |
Created at: March 4, 2026, 7:29 p.m.