Triple
T12625655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lopukhina |
E301505
|
entity |
| Predicate | hasFemaleForm |
P17779
|
FINISHED |
| Object | Lopukhina |
E301505
|
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: Lopukhina | Statement: [Lopukhina, hasFemaleForm, Lopukhina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lopukhina Context triple: [Lopukhina, hasFemaleForm, Lopukhina]
-
A.
Lopukhina
chosen
Lopukhina is a Russian noble family name historically associated with Eudoxia Lopukhina, the first wife of Tsar Peter the Great.
-
B.
Kashirina
Kashirina is a Russian surname most notably borne by Varvara Vasilyevna Kashirina.
-
C.
Lopatina
Lopatina is the feminine form of the Russian surname Lopatin.
-
D.
Kuntsevskaya
Kuntsevskaya is a Moscow Metro station on the Big Circle Line serving the Kuntsevo District in western Moscow.
-
E.
Shubskaya
Shubskaya is a Russian surname most notably associated with Anastasia Shubskaya, a film producer and the wife of hockey star Alexander Ovechkin.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9610a897c8190a96f3c78d4b270a2 |
completed | April 10, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6686d770881909850ffaf820171d9 |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:14 p.m.