Triple
T15845232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olga Ulyanova |
E384195
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ulyanova |
E389215
|
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: Ulyanova | Statement: [Olga Ulyanova, familyName, Ulyanova]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulyanova Context triple: [Olga Ulyanova, familyName, Ulyanova]
-
A.
Ulyanova
chosen
Ulyanova is a Russian surname most notably borne by the family of Vladimir Lenin, including his sister Maria Ulyanova.
-
B.
Lukyanova
Lukyanova is a Russian feminine surname derived from the masculine form Lukyanov.
-
C.
Vasilyeva
Vasilyeva is a common Russian surname, typically the feminine form of Vasilyev, derived from the given name Vasily.
-
D.
Tikhonova
Tikhonova is a Russian surname most prominently associated with Katerina Tikhonova, a public figure widely reported to be one of Vladimir Putin’s daughters.
-
E.
Korotkova
Korotkova is the family name of Kira Muratova, the acclaimed Soviet and Ukrainian film director and screenwriter.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14ca636048190bc89cd8b4efa89e9 |
completed | April 16, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa93fbcb481908e7b7ddc46992f79 |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.