Triple
T21286634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polina Semyonovna Zhemchuzhina |
E524676
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Polina |
—
|
NE NERFINISHED |
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: Polina | Statement: [Polina Semyonovna Zhemchuzhina, givenName, Polina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Polina Context triple: [Polina Semyonovna Zhemchuzhina, givenName, Polina]
-
A.
Aleksandra
Aleksandra is a feminine given name of Slavic origin, commonly used in various Eastern and Central European countries.
-
B.
Ksenia
Ksenia is a feminine given name, commonly used in Slavic countries and derived from the Greek name Xenia, meaning "hospitality" or "guest-friendship."
-
C.
Polina Zhemchuzhina
chosen
Polina Zhemchuzhina was a Soviet politician and influential figure in the early USSR, known both for her own party career and for being the wife of senior Soviet statesman Vyacheslav Molotov.
-
D.
Nadya
Nadya is a feminine given name, often used as a diminutive of Nadezhda in Slavic cultures.
-
E.
Alisa
Alisa is a feminine given name, often considered a variant of Alice, used in various cultures around the world.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d717c88190950bd48058912b65 |
completed | April 21, 2026, 8:35 a.m. |
Created at: April 16, 2026, 4:03 p.m.