Triple
T3923313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydia Lopokova |
E93211
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Lopokova |
E93211
|
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: Lopokova | Statement: [Lydia Lopokova, hasSurname, Lopokova]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lopokova Context triple: [Lydia Lopokova, hasSurname, Lopokova]
-
A.
Lopokova
chosen
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.
Kashirina
Kashirina is a Russian surname most notably borne by Varvara Vasilyevna Kashirina.
-
C.
Vladimira
Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
-
D.
Govardeyskaya
Govardeyskaya is a Moscow Metro station on the Kalininsko–Solntsevskaya line.
-
E.
Kuntsevskaya
Kuntsevskaya is a Moscow Metro station on the Big Circle Line serving the Kuntsevo District in western Moscow.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed7c2c848190a6d62e2df9b942d4 |
completed | March 9, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b53384bca08190af13ac3a417d8827 |
completed | March 14, 2026, 10:08 a.m. |
Created at: March 9, 2026, 3:23 p.m.